# Master Kill Switch Registry — Rulings of 2 September 2026

**The 420 Code · Studio G · 2 September 2026 · the registry desk, on the author’s delegation**

**Standing.** The author has delegated registry housekeeping and grading rulings to the desk (2 September 2026: "this is what you are for"). These rulings are made from the files, stated with their reasons, and stand until he overrules them. The registry itself is not rebuilt here: one build follows AP48, as he ruled.

## 1 — The registry of record

Master_Kill_Switch_Registry_v5_26_20260711.docx, digest b9a2eb60…, dated 11 July 2026: 561 switches; 545 live; 277 across 43 Artist's Proofs (Section I); 28 in Section II. Verified in hand. This is the last built registry and the base of the next build.

## 2 — The v1.23 collision, ruled

Root v1.23 (11 August 2026) recorded a collision: its own v1.22 entry closed at "(v5.26, 561)" while AP44's documents and the verifier's canon-sync keyed to v5.25/560, and it left two branches open — pointer drift (AP44's lock advance then standing as v5.26 · 567, as PROV-CCC.7 §7 declared) or a real v5.26/561 registry (the advance then renumbering to v5.27 · 568 with an erratum owed in PROV-CCC.8).

**Ruling: the second branch.** A real v5.26/561 registry exists, dated 11 July 2026, in the author's archive, and it pre-dates AP44's lock. AP44's seven switches (KS-CCC.1–.6, .4 split a/b) are not in it and could not have been. Therefore AP44's lock advance is v5.27, not v5.26; PROV-CCC.7 §7's "v5.26 · 567 · 44 · 47" is pointer drift on the version label — the counts it declares (561 + 7 = 568? no: 560 + 7 = 567) were computed on the v5.25 base and are one short; an erratum line is owed in PROV-CCC.8 stating both corrections. Nothing in AP44's claims moves; this is a label and a count.

## 3 — The next build, prospectively (v5.27, after AP48)

Base: v5.26, 561. Entering at the build, in lock order: AP44's seven (KS-CCC.1, .2, .3, .4a, .4b, .5, .6) → 568 across 44 Artist's Proofs. AP47's four (KS-FLIP.1–.4; KS-30.2 inherited, not new) → 572 across 45. AP45's four (KS-BLINK.1–.4) → 576 across 46. AP46's four (KS-STRETCH.1–.4; .4 registered for AP48) → 580 across 47. AP48's set at its lock, count unknown. One status update, no count change: KS-NPP.1 (AP30 / Predictions Part III), LIVE — STRUCTURAL → FIRED, 2 August 2026, 7.24σ, with its shown-corpse convention. Debts entering: D-CCC.1–.4 (.4 PAID by the closure note of this date), D-BLINK.1–.3 (.3 PAID by AP47), D-STRETCH.1, D5 CLOSED at the wave on AP44/AP45/AP46.

**Two conventions the build must add**, because v5.26's status taxonomy has neither. FIRED — the falsification condition was met; the switch stands on the board as a shown death, counted outside the live total, never repaired, never deleted; a new structural limb may freeze beside it as a new entry (AP47's row beside KS-NPP.1 is the first instance). REGISTERED — a switch entered by one paper on behalf of a future one, fireable only when the future paper exists (KS-STRETCH.4 for AP48 is the first instance); counted within the live total as LIVE — DEPENDENT, in the existing qualifier.

## 4 — The grading rulings

**AP45 The Blink.** LOCKED at composite 9.0. Weakest link: the falsification register. The proof owns no nature-facing switch; its empirical exposure is inherited (the Born rule's, on AP25's KS-56 and AP01's KS-V.3 — one test on two entries) and its structural switches wait on D-CCC.1. **The AP30/KS-30.1 precedent, under which AP44 locked at 9.3 with D-CCC.1 open, is ruled not to extend to inherited-only exposure.** AP44 carried three nature-facing switches of its own (KS-CCC.3, .4a, .4b); a paper that by its own honest genre claims no number cannot be graded on the falsification axis as though it had passed a test it never set. The ceiling is declared on the paper's face (§13, the lock line) and lifts when D-CCC.1 is written or the possibility face yields an independent consequence.

**AP46 The Stretch.** LOCKED at composite 9.0. Weakest link: the provenance of the lane count — adjudicated by the target on the night, with the prior ruling that fixed it stated beside it (§7) — and the H₀ seam, open until AP48. The paper's chain now carries a nature-facing edge fixed at this lock: one lane-time (0.66 Gyr) either side of the cycle, from the chain's own atom, with the seam stated in numbers — the corpus's H₀ = 74.3 under the standard history gives 12.52 Gyr, two lanes below the cycle. That edge is real and reachable, and it is the reason the paper locks at 9.0 rather than lower; it is also the reason it does not lock higher, since the seam is the family's most exposed joint and it is not yet closed.

**Both lock below the bar of 9.3 with the ceiling declared and the reason named**, which is the house's own pattern (AP44's lock line; the reviewer's stated position: locking with the ceiling declared is defensible; locking while claiming the bar is not). The reviewer's rescore of the locked versions is recorded in the Root when it arrives and does not reopen the lock; a finding that requires a change is a dated supersession.

## 5 — Provenance

Made from: the registry file (b9a2eb60…), Master Root v1.23–v1.25, AP44 FINAL v1.0, AP45 FINAL v1.7, AP46 FINAL v1.5, AP47 FINAL v3, the reviewer's passes of 2 September. The author may overrule any line here by a dated note; nothing in this instrument moves a claim.

*Frozen files are never edited; corrections supersede, dated, in the open.*