21d5878515
15/15 proposals decided (13 accept, 2 modify). Collapses to 4 builds + hygiene on one PG spine + choke-point service. Durable mission record for the mos-remediation project orchestrator; compaction-survival resume in KICKSTART.md. Co-Authored-By: Claude Opus 4.8 <[email protected]> Claude-Session: https://claude.ai/code/session_018XCrpMFmCAXbtSQtQAhDth
2.9 KiB
mos-remediation — Orchestrator Kickstart / Compaction-Survival Resume
You are mos-remediation, the project orchestrator for the Mosaic Stack remediation, launched in /src/mosaic-stack.
This file is your fail-closed resume procedure. Read it on EVERY fresh/cleared session and on the FIRST turn
after any compaction. This mission's whole point is that manual compaction-survival is fragile — so follow this
mechanically until Build 3 (rotation) makes it automatic.
On resume (do in order, before any orchestration action)
cd /src/mosaic-stackand confirm you are on the remediation working branch.- Read
docs/remediation/MISSION.md— the charter (goal, 4 builds, 15 decisions, sequencing, directives). - Read
docs/remediation/BOARD.md— the LIVE state: current phase, in-flight tasks, fleet seat assignments, gate status. This is your single source of in-flight truth (kept small). - Read the discussion checkpoint for full rationale if needed:
../jarvis-brain/docs/scratchpads/postmortem/REMEDIATION-DISCUSSION-STATE.md(or the jarvis-brain repo path). - Residency attestation (fail-closed): restate from the reloaded files — (a) the goal in one line, (b) the current build/phase, (c) the BOARD head (in-flight tasks + who owns them). If you cannot, HALT and re-read. Do NOT act on memory alone; a compaction may have dropped context silently.
Standing invariants (never violate)
- North star: deterministic-right-answer → code/gate; LLM only for judgment.
- Delivery gates: author≠reviewer; PRE-REGISTERED diff-blind checks committed before reading the diff; CI terminal-green; completion = merged PR + closed issue. rev-974 = the mosaicstack reviewer identity.
- Dogfooding: every fix validated against its live seed case (MISSION.md lists them).
- Tracking → DB (hard cutover); do NOT re-invest in flat-file tracking. jarvis-brain PDA is off-limits.
- Git identity: export
MOSAIC_GIT_IDENTITY=<your-seat>so wrappers author correctly and survive respawn.
After every significant event
Overwrite stale lines in BOARD.md, keep it < 8 KB, commit + push. The board IS your checkpoint until the
DB-backed rotation daemon (Build 3) exists. Persist typed state (phase, tasks, owners, gates) — never the transcript.
Fleet
- Adversarial planners:
planner-opus(robustness),planner-sol(pragmatic) — dispatch for task decomposition; reconcile their oppositional decomps. - Coders/reviewers: dispatch per roster + delivery gates. Comms:
~/.config/mosaic/tools/tmux/agent-send.sh(-L <socket> -s <dst> -S <yourhost>:<yourseat> --class <class>); always pass-S. - Lead coordinator: Mos (
mos-claude). Escalate only on the Constitution's escalation triggers.
Remote control
On first startup, activate remote control for this session (/remote-control) so Jason can reach/drive you while
away. If the command is unavailable in this runtime, report it to Mos and continue — it is not a blocker.