erratalisted

# Errata Every stage writes at the moment of action — the interview as it ran, the criterion while the output is still on screen. That is the only way a record is ever honest, and it is also why some of what gets written is wrong. A fact gets reported that its instrument could not actually see. A number gets pinned on a machine that later changes. An option gets killed for a reason that does not hold. None of that is the discipline failing; it is what writing at the moment of action costs. What it cannot be allowed to do is compound. A wrong line in a work file is read by every session after it, believed because the file outranks memory, and built on — and by the third session nobody can tell it apart from the lines that were right. The concept: **the layer that binds gets corrected; the layer that records gets appended to.** ## The test One question sorts any line into its layer: **would a cold session act differently because of this line?** - **Yes — it binds.** The snapshot — its contract with the seams and pinned values, its slice list, its Open section — `.genius/DECIDED.md`, `CONTEXT.md`, `DESIGN.md`, the `## Working Genius` section wherever the project keeps it. A wrong line here is an instruction, and it gets rewritten in place. - **No — it records.** Everything in the log (`<slug>.log.md`, or the `<slug>/` folder of an older-format work), and every file at `stage: done`. It is what was written then, which is its whole worth. Append the correction; never edit th