Handoff: make the POST-S27 block genuinely the sole source
The top block claimed to be "the only place" the new state is given, then §1.4, §2.6, §4.3 and §1.5 restated current S27/S16/collision status anyway. Rather than weaken the claim to match the text, the later sites are reduced to closure pointers -- duplicated live state is the defect this whole sequence has been about. - §1.4 now gets the same treatment as §1.2: the ORIGINAL pre-S27 chain diagram is restored as a dated record under a section-level supersession marker, and the in-place rewrite is removed. This also covers the rest of §1.4, which was already stale in ways nothing had marked -- S27's "still DRAFT, now dispatchable" line and the three inherited items it now discharges. - §2.6 and §4.3's collision notes reduced to "superseded -- see the collision row," with a pointer to §2.3, which remains the correct home for what actually blocks T1b and is unaffected. - §4.3 items 7 and 9 reduced to closure pointers. - §1.5 was a site nothing had touched: it stated S27 as UNBLOCKED and dispatchable as current fact. Now marked as an as-of-2026-08-07 snapshot with the ledger named authoritative per row. No new state is stated anywhere below the top block; every later mention is a supersession or closure marker. Documentation only. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ps1szk2mSfgp4Cz21eVH9x
This commit is contained in:
parent
9153623aa1
commit
af378d2d0f
|
|
@ -190,19 +190,17 @@ serialization already refused.
|
|||
one intentional hole in the refusal** and exists solely so a negative vector
|
||||
can contain the spelling it asserts is refused. Keep it private.
|
||||
|
||||
### 1.4 Chain state
|
||||
### 1.4 Chain state — SUPERSEDED 2026-08-09 by P13-S27 (`4df8e25`)
|
||||
|
||||
> **This whole section is a dated record.** The chain below, S27's status, and the three
|
||||
> inherited items it lists all describe the pre-S27 tree; **the three items are
|
||||
> discharged.** The current chain is in the **POST-S27 UPDATE at the top** and is not
|
||||
> restated here.
|
||||
|
||||
```
|
||||
format-epoch rung (LANDED) → P13-S27 (LANDED 4df8e25) → P13-S16 (UNBLOCKED — DRAFT, needs ratification)
|
||||
format-epoch rung (LANDED) → P13-S27 (UNBLOCKED, dispatchable) → P13-S16 (blocked on S27)
|
||||
```
|
||||
|
||||
> **Updated 2026-08-09.** It read `P13-S27 (UNBLOCKED, dispatchable) → P13-S16 (blocked
|
||||
> on S27)`. **S16 is unblocked but NOT dispatchable**: its contract
|
||||
> (`spec/CONTRACT_P13S16_PROJECTION.md`) is a DRAFT and must be ratified through
|
||||
> adversarial review rounds first. *Unblocked* and *dispatchable* are distinct here —
|
||||
> the S27 contract's own status block had to disambiguate them in round 1, which is how
|
||||
> it came to be ratified after a single round.
|
||||
|
||||
**P13-S27** — `spec/CONTRACT_P13S27_REDUCTION_AUTHORITY.md`, still DRAFT, now
|
||||
dispatchable. Its pin 2a was **resolved from outside** by the format rung's pin
|
||||
8, exactly as pin 2a's own prohibition required: *legacy bases are refused by
|
||||
|
|
@ -233,7 +231,9 @@ first time since it was filed.
|
|||
|
||||
### 1.5 Other open Pass-13 candidates
|
||||
|
||||
Ledger: `spec/PASS13_CANDIDATES.md`. Ten rows still read **open**: S4, S8, S9,
|
||||
Ledger: `spec/PASS13_CANDIDATES.md`. *(**Row states below are as of 2026-08-07 and are
|
||||
superseded for S27 and S16 — see the POST-S27 UPDATE at the top.** The ledger itself is
|
||||
authoritative for every row.)* Ten rows still read **open**: S4, S8, S9,
|
||||
S16, S18, S19, S23, S24, S25, S26. Beyond those, **S27 is UNBLOCKED and
|
||||
dispatchable** and **S28 is IMPLEMENTED** — both status openers were corrected in
|
||||
this handoff commit, because each still began "open" while its resolution sat
|
||||
|
|
@ -433,11 +433,8 @@ counts in `testkit/tests/requirement_labels.rs`, and — when T1b eventually
|
|||
opens — `epiphany-bundle`, which is exactly where §1's rungs live. ~~**T1b and
|
||||
P13-S27 both land in `bundle.rs` and must not fly together.**~~
|
||||
|
||||
> **RESOLVED 2026-08-09: S27 has landed, so there is nothing left for T1b to collide
|
||||
> with.** **This does not make T1b free** — it remains blocked on Ruling B blocker (ii),
|
||||
> versioned decode (§2.3, still accurate). The requirement-label surface is unchanged and
|
||||
> still shared. Any *future* `epiphany-bundle` rung re-creates a collision with T1b on
|
||||
> its own terms; that is a property of the crate, not of S27.
|
||||
> **SUPERSEDED 2026-08-09 — see the collision row of the POST-S27 UPDATE at the top.**
|
||||
> §2.3's account of what blocks T1b is unaffected and still current.
|
||||
|
||||
## §3. Reproducing the environment on the other machine
|
||||
|
||||
|
|
@ -528,23 +525,15 @@ work — this thread's whole method depends on a known-green baseline to mutate
|
|||
|
||||
**The two threads are independent right now** (§2.6) and can resume in
|
||||
parallel. ~~They collide only when T1b opens, since it and P13-S27 both land in
|
||||
`bundle.rs`.~~ **That collision is gone — S27 landed 2026-08-09.** T1b stays blocked on
|
||||
versioned decode (§2.3), and a future `epiphany-bundle` rung would create its own
|
||||
collision.
|
||||
`bundle.rs`.~~ **Superseded 2026-08-09 — see the collision row of the POST-S27 UPDATE.**
|
||||
|
||||
7. ~~**Spec thread — dispatch P13-S27.**~~ **DONE — landed and accepted at `4df8e25`**
|
||||
after eight independent reviews of the staged execution. It discharged the three
|
||||
inherited obligations *and* ended the no-canonical-base interval that had
|
||||
constrained every other piece of bundle work (§1.2).
|
||||
7. ~~**Spec thread — dispatch P13-S27.**~~ **DONE — see the POST-S27 UPDATE.**
|
||||
8. **Editor thread — run Round 2's checks**, whose apparatus is built and
|
||||
whose candidates are wired (§2.2); then Rounds 3, 3b, 4, 5 and the
|
||||
`RULING_EDITOR_TOOLKIT.md` verdict.
|
||||
9. Then **P13-S16** — **UNBLOCKED as of `4df8e25`, and now the head of the spec track.**
|
||||
It is **not** dispatchable yet: `spec/CONTRACT_P13S16_PROJECTION.md` is a **DRAFT**
|
||||
and needs ratification through adversarial review rounds first. **Its first act is
|
||||
bumping `CURRENT_REDUCTION_ALGORITHM_VERSION` to `1`**, since it changes
|
||||
`CreateStaffGroup`'s reduction verdict — that is what the authority S27 installed
|
||||
exists for.
|
||||
9. Then **P13-S16** — ~~dispatchable the moment S27 lands~~ **superseded 2026-08-09; see
|
||||
the POST-S27 UPDATE** for its current state, and
|
||||
`spec/CONTRACT_P13S16_PROJECTION.md` for what it now requires.
|
||||
10. Take a ruling on **S8** (reject one spelling vs. keep both canonical) whenever
|
||||
convenient — it needs a decision, not an implementation, and blocks nothing in
|
||||
the meantime.
|
||||
|
|
|
|||
Loading…
Reference in New Issue