mos-dt-0andClaude Opus 5
31c3191305
KICKSTART resume now points at origin/remediation/state for the live board, per Mos's cadence ruling: every tick is pushed to the rolling branch immediately (durable per-tick, no per-tick main PR); main carries periodic snapshots only. Reading the board from main would silently yield a stale tick, so the step warns explicitly. D-9 hardened: comms/v1 must use file/stdin transport, never argv interpolation. Standing interim rule until then — agent-send -f for any body with special characters, never -m. Mandatory in every worker brief alongside the D-8 clause. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
50 lines
3.4 KiB
Markdown
50 lines
3.4 KiB
Markdown
# 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)
|
|
|
|
1. `cd /src/mosaic-stack`, then **`git fetch origin remediation/state`**.
|
|
⚠ **The live board is on the rolling branch `remediation/state`, NOT on `main`.** `main` carries only
|
|
periodic snapshots, so reading the board from `main` will silently give you a STALE tick. Read the
|
|
live files at `origin/remediation/state` (e.g. `git show origin/remediation/state:docs/remediation/BOARD.md`),
|
|
or check that branch out. Every tick is pushed there immediately, so its HEAD is always the newest state.
|
|
2. Read `docs/remediation/MISSION.md` — the charter (goal, 4 builds, 15 decisions, sequencing, directives).
|
|
3. Read `docs/remediation/BOARD.md` **at `origin/remediation/state`** — the LIVE state: current phase,
|
|
in-flight tasks, fleet seat assignments, gate status. Single source of in-flight truth (kept < 8 KB;
|
|
older entries roll to `BOARD-LEDGER.md` via `board-roll.sh`).
|
|
4. Read the discussion checkpoint for full rationale if needed:
|
|
`../jarvis-brain/docs/scratchpads/postmortem/REMEDIATION-DISCUSSION-STATE.md` (or the jarvis-brain repo path).
|
|
5. **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.
|