118-the-renumber-is-history-not-a-standing-rule
The renumber is history, not a standing rule
Spec 095's acceptance asserts that the live corpus's ordinals are contiguous, `o == list(range(len(o)))`. Its requirement (3.3) is narrower: the one-time renumber left the survivors contiguous. Its own D-2 says reserved gaps are deliberate. Merging spec 117 while 105 to 116 stay reserved made the block red with no defect in the corpus. The repository owner ruled that the renumber is a historical transformation and not a perpetual contiguity rule (docs/release-candidate-0.22.0.md 10.1). This spec carries 095's block in full through `amends_verification`. The historical contiguity is read from the map that records it, and the live corpus is held to identity rules that survive growth, with fixture negatives showing each can still refuse. 095's requirements and block are not edited; its file gains only the superseded- acceptance note spec 082 3.4 requires.
Read the full pinned specification ↗Relationships
depended on by
amended by
Claimed units
No ownership claims exported.
Source headings
- 118: The renumber is history, not a standing rule
- 1. Purpose
- 1.1 A red block with no defect behind it
- 1.2 The owner's ruling
- 2. Territory
- 3. Behavior
- 3.1 The block is replaced in full
- 3.2 The historical renumber is read from the record of it
- 3.3 The live corpus is held to rules that survive growth
- 3.4 The engine still refuses what matters, shown on fixtures
- 4. Out of scope
- 5. Resolved decisions
- Verification
Frozen anchors
No frozen anchors declared.