Phase 8 — Consider That a Correction: the repair surface

"Consider that a divorce." Sometimes the right move is not to argue with the record — it is to fix it cleanly. Phase 8 adds the two human surfaces the earlier build proved were missing, and it relaxes no invariant to do it.

Tell the story. Facts render in filing order by default, which is not the order a human would use to explain a project. Narrative order lets the maintainer hand-arrange the facts on the panel — an order that survives supersession, so the story stays told even as individual facts change.

Repair a mis-recorded fact. A claim is immutable — but that rule created a trap: a mistyped predicate could only be fixed by a Retract, which writes a false "we were wrong" into the permanent record for a fact that was never actually wrong. Correction is the verb that was missing: fix what was recorded — its identity, date, and place — without ending anything or marking anything wrong.

Both repair surfaces are the human's, and that exposes an asymmetry: the agent cannot repair its own mistakes at all. The MCP write surface is create-only — no retract, no close, no supersede-of-existing, no correct. Every agent mis-file becomes operator work.

That was reviewed and kept on purpose (D8.7): the agent's write surface stays create-only; it is never handed cleanup or repair capability. What it gets instead is a voice — it surfaces a suspected mis-file to the human over the chat channel (Phase 9), and the human does the correcting. This is now route-layer-enforced: an agent key gets a 401 on close, retract, and merge. The one history verb the agent keeps is create-with-supersedes_id, which is additive — settled twice with the operator. The agent proposes; the human edits. It surfaces the mess; it never gets to quietly tidy it away.