the record · exhibit 19 · loop 01, Design
The off-by-two that would have broken the book
Renumbering thirty-four chapters into thirty-six moved the reveal schedule’s supreme rule by two chapters; the hazard was written down before any file was renamed.
· principles 2, 4 of twelve
What it shows
Principle four. Information release is a scheduled resource, and the schedule is pinned to chapter numbers. Renumbering thirty-four chapters into thirty-six moved the supreme rule by two chapters, onto the one chapter most explicitly forbidden to reach confirmation. The hazard was written before any file was renamed, along with the order in which the pins had to move.
The principles are numbered on the method page. Cuts in the excerpts below are marked with an ellipsis in brackets; the three kinds of cut are stated on the record’s front page.
From the record
## ★ HAZARDS — the ways this arithmetic can break the book **1. THE OFF-BY-TWO THAT WOULD DESTROY THE RESTRUCTURE.** `reveal-schedule.md`'s supreme rule reads *"Nothing reaches Confirmation before Ch 29."* Under the new numbering that rule means **Ch 31**. And **new Ch 29 is old Ch 27 — "Granted Access" — which the schedule flags as the *hard ceiling*, the last guard before the Point.** Anyone who applies the un-renumbered rule to the new sequence would be authorizing Confirmation **two chapters early, at the single chapter most explicitly forbidden to reach it.** Until the re-pin is executed, **any reveal-safety check must convert through this table first.** […] **4. `continuity-ledger.md` carries hundreds of `First appears: Act N Ch NN` stamps.** **Do not mass-renumber them** — a bulk edit of the fact register is the highest-risk operation in the repo. Prepend this conversion table to the ledger instead and leave the historical stamps in old numbering, explicitly labelled.