stack/docs/remediation/BOARD.md

mos-remediation — LIVE BOARD (keep < 8 KB)

Phase: EXECUTING — P0 open. RM-01 MERGED; RM-02 (keystone gate registry) is next. Updated: 2026-07-31 (mos-remediation orchestrator; seat active on mosaic-fleet).

Head

• Mission charter + 15 decisions + 4-build plan: PERSISTED (docs/remediation/MISSION.md).
• HOLD lifted for this workstream (Jason 2026-07-31). Nothing implemented yet — planning first.
• Orchestrator seat mos-remediation is LIVE and owns the mission. Residency attestation: PASS.
• TASK-0 DONE — checkout repaired, all three gates green HONESTLY (no --no-verify), branch pushed.
• TASK-1 DONE — both planners delivered independently on clean context; reconciled into TASKS.md (58 tasks across P0–P5, 7 convergences, 7 adjudicated disagreements, 3 escalated decisions).
• NEXT ACTION IS NOT MINE: DECISION-1/2/3 (TASKS.md §5) must be ruled before P0 dispatch. RM-01 is dispatchable immediately regardless — it depends on nothing and blocks everything.

In-flight

Task	Owner	State
RM-01 reproducible checkout	—	MERGED f58b3699 (PR #1027) — rev-974 APPROVE + CI #2172 8/8 green
RM-02 gate registry ★keystone	unassigned	READY — depends only on RM-01; not held by RM-03
RM-03 queue guard (3 defects)	—	HOLD — #1023 SUPERSEDED-PENDING-JASON
RM-59 close D-19 residual risk	—	BLOCKED by RM-12/RM-21/RM-25 (spine + executor) — tracked edge, not prose
remediation/state snapshot → main	mos-remediation	opening at this mission seam

Fleet seats

• mos-remediation — project orchestrator (Claude, /src/mosaic-stack, socket mosaic-fleet) — ACTIVE
• planner-opus — adversarial planner (robustness), Opus 5, socket default — DELIVERED, idle
• planner-sol — adversarial planner (pragmatic), gpt-5.6-sol, socket default — DELIVERED, idle
• rev-974 — mosaicstack reviewer identity (id 16, write:repository) — idle, on call
• Mos (mos-claude) — lead coordinator, socket default — relay path to Jason

Gate status

• Delivery gates active: author≠reviewer, diff-blind pre-registered checks, CI-green, merged-PR completion.
• Freeze: LIFTED for this workstream only.
• Git identity: MOSAIC_GIT_IDENTITY=mos-dt-0 INTERIM. Mos ruled gate-16 HOLDS (author≠reviewer is what gate-16 protects; rev-974 reviews, mos-dt-0 never self-reviews). Dedicated identity TRACKED, Mos provisions.
• Capability check (D-11b): before dispatching seat X to provider Y, verify ~/.config/mosaic/secrets/gitea-tokens/gitea-<Y>-<X>.token exists. Token-file set = authoritative capability registry. Mos owns provisioning; escalate missing pairs to him.
• Seat identity (D-11a): token identity AND git config user.name/user.email must BOTH be set and agree. Exporting MOSAIC_GIT_IDENTITY alone does NOT fix commit authorship.
• Standing worker-brief doctrine (accreted, mandatory in every brief): don't weaken a RED test to make it pass; if a check is unrunnable as written SAY SO, never silently substitute; agent-send -f never -m; heavy artifacts off shared /tmp.
• Remote control: native /remote-control NOT wired in this runtime. Path is Mos-relay (Jason ↔ mos-claude via Discord ↔ mos-remediation via agent-send). Not a blocker.

Sequencing (from MISSION.md)

1. Spine + choke-point service (MACP wiring @ mosaic_orchestrator.py::run_single_task) + PG/Redis ⚠ CONTESTED — see DECISION-1. Both planners independently reject this wire-in point: that controller is "enabled": false and references a dispatcher that does not exist here. Charter text left UNCHANGED pending Mos/Jason ruling; do not treat it as settled.
2. Rotation daemon (finish Mission Control Plane, reuse packages/coord)
3. Comms service (envelope→service→PG/Redis→adapters)
4. Hygiene + conformance harness Cross-cutting retirements: flat-file tracking, 3 MACP islands, silent MOSAIC BYPASS.

Dogfood evidence — live failure classes, not hypotheticals

Newest first. Oldest entries roll to BOARD-LEDGER.md via board-roll.sh when this file exceeds its 8 KB cap. Keystone detail is duplicated in TASKS.md §1a, so rolling loses nothing.

D-8 / P-CONFORMANCE-001 — a PRE-REGISTERED acceptance check that was not runnable as written.

PR #1025 AC2's fixture mkdir -p apps/*/venv/lib creates a literal apps/*/venv/lib dir when the glob is unmatched — it did not test what it claimed. rev-974 ran it exactly as written, caught it, re-ran the intended assertion at an explicit path, and disclosed rather than silently substituting a working fixture and reporting PASS. Pre-registration protects a check from being retrofitted to the implementation; it does not make the check correct. An unverified gate appeared inside the mechanism built to catch unverified gates. Hard requirement on RM-02: the registry must self-verify that every registered case runs AND can fail — presence is not evidence.

D-7 / P-FLEET-001 — stale-GC-on-disk: shared 30G /tmp hit 100% ENOSPC, degrading two seats.

~5.2G was session scratch dead 8-9 days (this session's own footprint: 88K). Same missing capability as orphaned-tmux-session GC, applied to disk — not a quota or discipline problem. Resolved manually by Mos (lead coordinator) after independent verification; /tmp now 79%. The gap IS the finding: the authority to reap exists, the deterministic reaper does not. Folded into RM-50 with explicit requirements (mechanical liveness, age threshold, dry-run, audit event per reap — never a heuristic sweep). Refusing to unilaterally delete another session's scratch was correct doctrine; the fix is a reaper, not braver agents.

D-6 / P-QUEUE-001 — the mandated queue guard returned PASS on an UNKNOWN state, live, today.

Running the required ci-queue-wait.sh --purpose push before pushing produced state=unknown ... exit 0 — the exact defect at ci-queue-wait.sh:282-288 that PR #1023 is parked on. It also evaluated branch=main rather than the branch being pushed. The mission's own required pre-push gate passed me on an indeterminate result. Third independent live instance of the class.

Decisions log

• 2026-07-31 — Mission set up by Mos post-postmortem (15/15 decided). Dogfood posture active.
• 2026-07-31 — Mos: stale .mosaic/orchestrator/mission.json is RESIDUE of the disabled Python orchestrator rail that this plan RETIRES. Do NOT invest in it; do NOT build on that rail. The 0/0 milestone banner is cosmetic. (Supersedes any plan to repair it.)
• 2026-07-31 — Mos: planners must be dispatched with GUARANTEED clean context, not requested-clean. Prior default-socket planner sessions predate this mission; dirty context is the indicted hygiene.
• 2026-07-31 — mos-remediation: worker briefs forbid all git ops and restrict each worker to a single named output file, so two planners can share one checkout without a branch race (M2-era incident doctrine).