mosaicstack/stack

Fork 0

Files

Jason Woltje b38cfac760

ci/woodpecker/push/ci Pipeline was successful

Details

ci/woodpecker/pr/ci Pipeline was successful

Details

feat: integrate framework files into monorepo under packages/mosaic/framework/

Moves all Mosaic framework runtime files from the separate bootstrap repo
into the monorepo as canonical source. The @mosaic/mosaic npm package now
ships the complete framework — bin scripts, runtime configs, tools, and
templates — enabling standalone installation via npm install.

Structure:
  packages/mosaic/framework/
  ├── bin/          28 CLI scripts (mosaic, mosaic-doctor, mosaic-sync-skills, etc.)
  ├── runtime/      Runtime adapters (claude, codex, opencode, pi, mcp)
  ├── tools/        Shell tooling (git, prdy, orchestrator, quality, etc.)
  ├── templates/    Agent and repo templates
  ├── defaults/     Default identity files (AGENTS.md, STANDARDS.md, SOUL.md, etc.)
  ├── install.sh    Legacy bash installer
  └── remote-install.sh  One-liner remote installer

Key files with Pi support and recent fixes:
- bin/mosaic: launch_pi() with skills-local loop
- bin/mosaic-doctor: --fix auto-wiring for all 4 harnesses
- bin/mosaic-sync-skills: Pi as 4th link target, symlink-aware find
- bin/mosaic-link-runtime-assets: Pi settings.json patching
- bin/mosaic-migrate-local-skills: Pi skill roots, symlink find
- runtime/pi/RUNTIME.md + mosaic-extension.ts

Package ships 251 framework files in the npm tarball (278KB compressed).

2026-04-01 21:19:21 -05:00

1.9 KiB

Raw Permalink Blame History

Mosaic Matrix Orchestrator Rail

Runtime-agnostic orchestration rail for delegating work to worker agents and enforcing mechanical quality gates.

Purpose

Decouple orchestration from any single agent runtime feature set
Persist state in repo-local .mosaic/orchestrator/ files
Emit structured events for Matrix transport and audit trails
Enforce rails before marking tasks complete

Components

protocol/ - JSON schemas for task/event payloads
controller/mosaic_orchestrator.py - deterministic controller loop
adapters/ - runtime adapter guidance

Repo Contract

The controller expects this layout in each bootstrapped repo:

.mosaic/orchestrator/
  config.json
  tasks.json
  state.json
  events.ndjson
  logs/
  results/

Quick Start

From a bootstrapped repo:

~/.config/mosaic/bin/mosaic-orchestrator-matrix-cycle
~/.config/mosaic/bin/mosaic-orchestrator-run --once
~/.config/mosaic/bin/mosaic-orchestrator-drain

Continuous loop:

~/.config/mosaic/bin/mosaic-orchestrator-run --poll-sec 10

Sync from docs/TASKS.md to queue:

~/.config/mosaic/bin/mosaic-orchestrator-sync-tasks --apply

Set worker command when needed:

export MOSAIC_WORKER_EXEC="codex -p"
# or
export MOSAIC_WORKER_EXEC="opencode -p"

Publish new orchestrator events to Matrix:

~/.config/mosaic/bin/mosaic-orchestrator-matrix-publish

Consume Matrix task messages into tasks.json:

~/.config/mosaic/bin/mosaic-orchestrator-matrix-consume

Matrix Note

This rail writes canonical events to .mosaic/orchestrator/events.ndjson. The Matrix transport bridge publishes those events into the configured control room and can consume task commands from that room.

Task injection message format (room text):

!mosaic-task {"id":"TASK-123","title":"Fix bug","command":"echo run","quality_gates":["pnpm lint"]}

1.9 KiB Raw Permalink Blame History