mosaicstack/stack
1
0
Fork 1
Code Issues 140 Pull Requests 5 Actions Packages Projects Releases 15 Wiki Activity

docs(remediation): board — RM-02 frozen at 38f1b249 with a fully clean 9/9 scan

Browse Source 
First run on this branch where ci-postgres passed, so no exemption question arises.
Recorded that the artifact's intermittency is evidence FOR RM-61's negative-control
requirement: intermittent means delivery is a coin flip until the signature is proven to
discriminate from a real database failure.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
This commit is contained in:
mos-dt-0
2026-08-01 00:35:51 -05:00
co-authored by Claude Opus 5
parent c83a3cd3e2
commit eddf718a5c
1 changed files with 14 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/remediation/BOARD.md
+14 -13
View File
@@ -1,6 +1,6 @@
# mos-remediation — LIVE BOARD (keep < 8 KB)
**Phase:** EXECUTING — RM-02 FROZEN at `9b4d4beb`, CI green, review in flight; RM-03 implementing.
**Phase:** EXECUTING — RM-02 FROZEN @ `38f1b249` (CI 9/9 clean, review in flight); RM-03 fixing 1 blocker.
**Updated:** 2026-07-31 (mos-remediation orchestrator; seat active on `mosaic-fleet`).
## Head
@@ -16,19 +16,20 @@
## In-flight
| Task | Owner | State |
| ------------------------------- | ------------- | --------------------------------------------------------------------------- |
| RM-01 reproducible checkout | — | **MERGED** `f58b3699` (#1027) |
| RM-02 gate registry ★keystone | rev-974 | **FROZEN** @ `9b4d4beb`; CI #2182 SUCCESS 8/8 functional; review in flight |
| RM-03 queue guard | coder-mos1 | implementing; CANNOT_ASSERT ruled **B**; build to READY then HOLD for Jason |
| RM-59 D-19 residual risk | — | blocked on RM-12/21/25 |
| RM-60 / #1031 CI trust boundary | Jason (infra) | option **B**; A does not fix the ordering defect |
| #1023 queue-guard attempt | Jason | SUPERSEDED-PENDING-JASON — live REQUEST_CHANGES; do **not** merge |
| 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 |
**RM-02 head-triple verified (twice, independently — orchestrator + f10-coder):** local = origin =
PR #1030 = pipeline #2182 = `9b4d4beb0e0a…`. `Closes #1029` present. Full step scan, not a
tests-complete inference. `ci-postgres` FAIL read as the D-21 teardown artifact (test log shows
PostgreSQL accepting connections; test step OK). Queue guard **not** offered as evidence.
**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.
## Delivery gates — DOCTRINE CHANGE 2026-08-01