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 payloadsdispatcher/- MACP dispatch helpers for worktrees, command generation, results, and cleanupcontroller/mosaic_orchestrator.py- deterministic controller loopadapters/- 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"]}
MACP Notes
MACP-aware tasks add dispatch metadata on top of the existing queue model:
dispatch:exec,yolo, oracptype: task category used for orchestration intentworktree/branch: task-specific git execution contextbrief_path: markdown brief consumed by runtime-backed dispatchersresult_path: structured result JSON written under.mosaic/orchestrator/
Controller behavior remains backward compatible:
- Tasks without
dispatchcontinue through the legacy shell execution path. - Tasks with
dispatchuse the MACP dispatcher and can emittask.gatedandtask.escalated.
Manual queue operations are exposed through:
mosaic macp submit ...
mosaic macp status
mosaic macp drain
mosaic macp history --task-id TASK-001