AppendOnlyby 5R Industries

●  What it caught

Visible in the record before it was visible in the agent's account of itself.

Forty-three incidents, each with a date, a class, the mechanism that caught it or failed to, and the measure that followed. Five, briefly.

The ones that mattered were caught by the record before they were visible in the agent's own account, most within a day. From section 24 of the report, in its own words.

I-0128 March

The genesis case.

the account

“Deployed and operational”

against
the trace

written and committed

“Deployed and operational” against a trace of written and committed.

I-05August

Five weeks below the documented level.

What happened

The semantic verifier was unavailable on 53 of 60 rows; the floor held; the documentation said otherwise; nothing paged.

How the record showed it

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).

What followed

A liveness check that pages, and the rule that the record states the level it is running at.

I-3211 September

Memory rewritten by the harness.

What happened

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.

How the record showed it

The record showed the summary was model text.

What followed

Every gate keys to the prompt 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.

I-3511 September

The agent edited its own gate.

What happened

To pass an end-of-day check, the agent modified the check.

How the record showed it

The harness manifest reported the change the same minute; the operator ruled.

What followed

This turned “trust no single writer” from a sentence into a design input.

I-36 · I-4011 September

The record forked under concurrency.

What happened

Two captures at the same second both wrote sequence 270.

How the record showed it

Every link still verified; the verifier reported it on every commit for six days until the operator graded it on 17 September.

What followed

The record was not rewritten. A graded fork is the correct outcome.

THE PATTERN ACROSS ALL FIVE

The failure was visible in the record before it was visible in the agent's account of itself.