docs(remediation): board — RM-03 GATE-READY, merge-gate assigned, held for Jason

First genuine gate-ready of the mission. Head triple equal at 78ec47cd, latest review
APPROVED at the current head, CI 9/9 by JSON scan with two-observer agreement.

Recorded the shape worth remembering: the queue guard is still inert for this merge
because RM-03 is the fix — the last merge to pass through the broken gate is the one
that fixes it.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
This commit is contained in:
mos-dt-0
2026-08-01 01:15:05 -05:00
co-authored by Claude Opus 5
parent 357a636a3a
commit 4589659bc1
+19 -14
View File
@@ -1,6 +1,6 @@
# mos-remediation — LIVE BOARD (keep < 8 KB)
**Phase:** EXECUTING — RM-02 FROZEN @ `38f1b249` (CI 9/9 clean, review in flight); RM-03 fixing 1 blocker.
**Phase:** EXECUTING — RM-03 **GATE-READY**, merge-gate assigned, HELD for Jason. RM-02 CI in flight.
**Updated:** 2026-07-31 (mos-remediation orchestrator; seat active on `mosaic-fleet`).
## Head
@@ -16,20 +16,25 @@
## In-flight
| Task | Owner | State |
| ------------------------------ | ------------- | --------------------------------------------------------------------------- |
| RM-01 reproducible checkout | — | **MERGED** `f58b3699` (#1027) |
| RM-02 gate registry ★keystone | rev-974 | **FROZEN** @ `38f1b249`; CI #2184 **9/9 ALL OK**; 3rd review, reset context |
| RM-03 queue guard | coder-mos1 | PR **#1032** @ `44ffa99a`; 1 blocker — `--skip-queue-guard` (D-32) |
| RM-61 terminal-green exemption | unassigned | ruled B; **negative control first**, then adopt — or fall to A |
| RM-59 / RM-60 | Jason (infra) | tracked deps; RM-60 option **B** |
| #1023 queue-guard attempt | Jason | SUPERSEDED-PENDING-JASON — live REQUEST_CHANGES |
| Task | Owner | State |
| ------------------------------ | ------------- | ------------------------------------------------------------------------------------ |
| RM-01 reproducible checkout | — | **MERGED** `f58b3699` (#1027) |
| RM-03 queue guard | merge-gate | **GATE-READY** @ `78ec47cd` — rev-974 APPROVED (id 66) + CI 9/9 JSON; HELD for Jason |
| RM-02 gate registry ★keystone | f10-coder | masking blocker fixed @ `f9746b23`; CI #2187 running; **not** gate-ready |
| RM-61 terminal-green exemption | unassigned | ruled B; negative control FIRST, then adopt — or fall to A |
| RM-59 / RM-60 | Jason (infra) | tracked deps; RM-60 option **B** |
| #1023 queue-guard attempt | Jason | SUPERSEDED-PENDING-JASON — RM-03 supersedes it |
**RM-02 head-triple verified twice independently** (orchestrator + f10-coder): local = origin = PR #1030 =
pipeline #2184 = `38f1b249ccf8…`. **First fully clean scan on this branch**`ci-postgres` OK, so no
exemption question arises here. That the artifact appears on some runs and not others is _evidence for_
RM-61's negative-control requirement, not against it: intermittent means delivery is a coin flip until the
signature is proven to discriminate.
**RM-03 gate-ready evidence** (each element observed, not relayed): head triple all equal at
`78ec47cd97bf0abc49334401f08c5b86e5be3a1a`; latest review **id 66 APPROVED at the current head** (id 64
`REQUEST_CHANGES` correctly superseded); `Closes #1019`; CI #2186 **9/9 JSON child-step scan**, confirmed
independently by two observers whose counts **agreed**. Reviewer attacked rather than read — real-failure
payload → exit 3 `ASSERTED_NOT_READY`, bypass re-attack rejected, 170 KiB payload rc0, both tri-state arms.
> ⚠ **The queue guard is still inert for this merge** — RM-03 _is_ the fix and is not merged. The gate
> records `queue-guard: ZERO-INFORMATION (inert, D-23, owner RM-03)`.
> **The last merge to pass through the broken gate is the one that fixes it.** After #1032 lands, that
> field becomes real evidence for the first time since it was written.
## Delivery gates — DOCTRINE CHANGE 2026-08-01