stack

Files

T

mos-dt-0andClaude Opus 5 24a7915633 docs(remediation): stop item 1 restating the In-flight table — it went stale 3x by duplicating it

Item 1 has now gone stale three separate times in one session, every time for the same reason: it
restated lane state that the In-flight table already owns. That is D-26's class (restatement is lossy
every time) and D-43's mechanism (a second copy is a second thing to go stale). Fixing the wording a
fourth time would just buy another few hours.

So it no longer carries lane state at all — it points at the table and keeps only the two things that
are NOT restatements: read the table, and re-derive any board claim from the provider before
load-bearing use, because the board is sole-written and has no independent verifier.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>

2026-08-01 11:49:32 -05:00

AC-RM02-HARDENING.md

docs(remediation): pre-register the RM-02 hardening re-review — attack the FIX, not the original bug

2026-08-01 11:32:35 -05:00

AC-RM02-REBASE.md

docs(remediation): pre-register RM-02 keystone review ACs before the reviewer reads the diff

2026-08-01 10:24:24 -05:00

AC-RM61-REREVIEW-033b2ffb.md

docs(remediation): bank D-37/D-38, pre-register RM-61 re-review, rebuild board for a cold read

2026-08-01 08:59:40 -05:00

AC-RM61-TYPESTRICT.md

docs(remediation): D-40 RULED BLOCKING; pre-register type-strict ACs before the fix is pushed