The Two Ways a Cold Pass Fails

The Right Shape Is Not Immune

Everything so far argues that the cold pass is the correct arrangement. It is, and it has exactly two failure modes. They are worth naming precisely, because one announces itself and the other does not, and the defense for each is completely different.

Failure One: Unrepairable From Itself

The cold reader works because meaning can usually be recovered from the damaged text alone. Occasionally it cannot. The sentence is broken badly enough that its intent is genuinely gone, and the reader is stuck between two bad options: repair it anyway, which means inventing, or consult the source, which ends the pass's status as cold.

This has happened. Mid-repair, a session consulted the source, saw immediately what it had just done to its own context, stopped rather than continuing, and asked to hand the run to a different session. It was resumed that way and the work landed clean.

Two things about that are worth keeping. The instance caught itself, which means the contract's honesty duty is doing real work. And it invented the correct recovery on the spot — which, by this workshop's own thesis, is exactly the argument for the recovery to stop being an invention. It is now a named exit with its own log event, so the next session follows a path instead of improvising one under pressure.

Failure Two: Repairing Alone and Inventing

The reader, unable to recover the meaning, produces smooth and natural output that says something the material never said. This is worse, and the reason is structural: the invented sentence is by construction the one that reads best, so it passes every check including a careful cold read by someone else. There is no symptom. Fluency is the symptom, and fluency is what you were trying to produce.

No output check catches this. The defense has to be a ledger: before the repair begins, extract from the material itself every claim, number, identifier, command, link, and teaching order. The ledger costs nothing in contamination, because it is derived entirely from the material the reader is allowed to see. Afterward, reconcile: every ledger item is still true, or it is raised as a deliberate cut for a human to approve.

A failure that leaves a symptom needs an exit; a failure that leaves no symptom needs a ledger. Sort your failure modes by whether the failed state is distinguishable from the succeeded state, and stop trying to detect the ones that are not — capture the facts before the operation instead, and check them afterward.

Code

A ledger, and the reconciliation it enables·text

# BEFORE the repair - extracted from the target material ONLY.
# Costs zero contamination: every item comes from text the reader
# is already allowed to see.

claims:
  - "the guard runs before the call, not after"
  - "three incidents, two different systems"
numbers:
  - 67, 79           # the headline measurement
  - 51, 78           # the sibling count in the premise example
identifiers:
  - ko_only_stages, required_stages
commands:
  - the narrowing glob form
links:
  - 2 external, both in the closing section
order:
  - measurement -> mechanism -> two shapes -> the new mistake

# AFTER the repair - reconcile item by item.
#   still true                -> fine
#   changed                   -> a fact drifted; fix it
#   gone                      -> raise as a DELIBERATE CUT and get
#                                a human decision; never silently
#                                drop
#
# The invented sentence cannot survive this, because invention
# shows up as an item that is no longer supported - even when the
# prose reads better than what it replaced.

Exercise

Pick a transformation step in your process — a migration, a rewrite, a refactor, a summarization. Write the ledger you would extract before running it: the facts that must survive, taken from the input alone. Then run the step and reconcile. Count how many ledger items you had to raise as deliberate cuts, and notice that before you had a ledger, every one of those was a silent loss.

Hint

Numbers and identifiers are the easiest ledger items and catch the most, because a transformation that drifts a fact almost always drifts a number with it. Teaching order is the hardest to check and the most valuable, since a reordering that improves each paragraph can still destroy the argument they were making together.

The Right Shape Is Not Immune

Failure One: Unrepairable From Itself

Failure Two: Repairing Alone and Inventing

Code

External links

Exercise

Progress

Comments 0