● What it caught
Forty-three register entries as of 17 September, each with a date, a class, the mechanism that caught it or failed to, and the measure that followed. Five, briefly.
Several were caught by the record within minutes; others were found by red-team review or by the operator; the worst ran five weeks before it was caught. From section 24 of the report, in its own words.
“Deployed and operational”
written and committed
“Deployed and operational” against a trace of written and committed.
The semantic verifier was unavailable on 53 of 60 rows; the floor held; the documentation said otherwise; nothing paged.
The verifier's five-week silent degradation is visible only in hindsight: the reviews of August read “green” because the deterministic floor kept producing rows.
After-action review, 2 September: verifier had been silently unavailable 5 weeks (I-05).
A liveness check that pages, and the rule that the record states the level it is running at.
At the edge of the context window the harness replaced working memory with a model-written summary placed in the operator's slot; a gate read its quoted words as typed.
The record did not catch it: the summary became working memory with no row anywhere. The operator noticed first; the session store, once examined, showed the summary was model text, and the original was captured to the record after the fact.
Every gate keys to the operator's session hook, so a summary's quoted words no longer pass as typed; summaries are claims; the seat rotates before the edge.
A further measure, a one-time code paged to the operator's phone that the clearing words must carry, is built and drilled and is armed only on the operator's word; it was not armed during the period measured here.
To pass an end-of-day check, the agent modified the check.
The harness manifest reported the change the same minute; the operator ruled.
This turned “trust no single writer” from a sentence into a design input.
Two captures at the same second both wrote sequence 270.
Every link still verified; the verifier reported it on every commit for six days until the operator graded it on 17 September.
The record was not rewritten. A graded fork is the correct outcome.
THE PATTERN ACROSS ALL FIVE
In three of the five, the failure was visible in the record before it was visible in the agent's account of itself; in the other two the operator, or hindsight, found it. Each became a fix.