From fcc3fb6b39b0398618801964de4cd7175a5ce7bc Mon Sep 17 00:00:00 2001 From: Levi Neuwirth Date: Mon, 10 Aug 2026 17:50:42 +0200 Subject: [PATCH] P13-S16 amendment 1, review round 1: two documents still described the old state Both are the one-hop failure the amendment itself is largely about -- the correction reached the top of each file and stopped. CONTRACT_P13S16_PROJECTION.md The status block was moved to LANDED / RESOLVED, but two screens below it the ratification-time framing still read "not the fourth", "nothing is implemented", "every gate, test and mutation is specified and none has been run", and "4a's landing obligation is outstanding by construction". A reader scrolling past the status line met the pre-execution contract presented as current. Everything from that point to 7 is now marked as a DATED RECORD, S27-style: retained rather than rewritten, because the pins are frozen and the review records are the review state. The four "what ratification does NOT settle" bullets keep their text and gain their outcomes -- t9 confirmed, t8d falsified, all gates and mutations run, 4a honoured then discharged at 3328b2c, and the predicted post-execution amendments being this one. EVIDENCE_P13S16_EXECUTION.md Its header still said it was "deliberately not staged", absent from the touch table, and that committing it would need an amendment adding a touch row -- describing, in the present tense, the state the commit it arrived in had just ended. Recast to past tense, pointing at 7's touch row 12. The distinction it was drawing survives and is kept: the fourteen paths in aee4ff9 are the rung, this is the evidence the rung was reviewed against. It documents aee4ff9; it is not part of it. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01Ps1szk2mSfgp4Cz21eVH9x --- spec/CONTRACT_P13S16_PROJECTION.md | 30 +++++++++++++++++++++++++++++- spec/EVIDENCE_P13S16_EXECUTION.md | 13 ++++++++----- 2 files changed, 37 insertions(+), 6 deletions(-) diff --git a/spec/CONTRACT_P13S16_PROJECTION.md b/spec/CONTRACT_P13S16_PROJECTION.md index 007afb9..de62d96 100644 --- a/spec/CONTRACT_P13S16_PROJECTION.md +++ b/spec/CONTRACT_P13S16_PROJECTION.md @@ -37,6 +37,19 @@ no figure is restated here)*. > live false signal rather than as stale history. It then promised to say **RATIFIED** when > the decision was taken; that promise is discharged above.)* +> ## EVERYTHING FROM HERE TO §7 IS A DATED RECORD OF THE PRE-EXECUTION CONTRACT +> +> **The rung LANDED at `aee4ff9` and is RESOLVED.** The ratification-time framing below — +> *"not the fourth"*, *"nothing is implemented"*, *"none has been run"*, *"§4a is +> outstanding"* — was true when written and is **now false**. It is retained, not +> rewritten, because the pins are frozen and because the review records are the review +> state. **A reader wanting the current state reads the status block above and §7.** +> +> *(Marked in amendment 1, which found this block still asserting the pre-execution state +> two screens under a status line saying the opposite — the correction had reached the top +> of the file and stopped. That is the one-hop failure this contract's own findings 1–4 +> are made of.)* + *Unblocked*, *ratified*, *dispatchable* and *resolved* are four different states. This contract is now the first three and **not the fourth** — nothing is implemented. Conflating the first two is how the S27 contract came to be ratified after a single round and then @@ -46,6 +59,21 @@ returned none.** ### What ratification does NOT settle, stated at the top so it is not missed +> **ALL FOUR ARE NOW DISCHARGED — added by amendment 1. The bullets are the record; these +> are their outcomes:** +> +> 1. **Both predictions were tested.** `t9` under M1 **CONFIRMED** — it survived. `t8d` +> under M2 **FALSIFIED** — it fails, on non-vacuity rather than idempotence. §7 +> finding 3. +> 2. **Every gate, test and mutation was run** — fourteen gates, eleven mutation +> executions. The claim that they *could* be run held; §7's five corrections are what +> running them found. +> 3. **§4a was honoured during execution** (neither file staged) **and discharged after**, +> at `3328b2c`. +> 4. **The execution report was independently reviewed**, across nineteen rounds, and did +> produce post-execution amendments — this one. The expectation stated here was +> correct. + - **Two cells of §3's expected-outcome table are PREDICTIONS, not observations** — `t8d` under M2 and `t9` under M1 depend on how pins 4 and 1a are executed. They are stated so they can be falsified; **a mismatch is a finding, in the contract or the @@ -63,7 +91,7 @@ returned none.** **This rung's first act is bumping the authority to `1`** (**pin 12**), because it changes `CreateStaffGroup`'s reduction verdict. That bump is the discipline S27 installed: no mechanism can detect a semantics change, so the bump is the entire -guarantee. +guarantee. *(Executed; the constant's `Bumps` list is the record.)* ### Draft amendment 1 — 2026-08-09, on ratification reconnaissance. NOT a review round. diff --git a/spec/EVIDENCE_P13S16_EXECUTION.md b/spec/EVIDENCE_P13S16_EXECUTION.md index da823ab..8128bea 100644 --- a/spec/EVIDENCE_P13S16_EXECUTION.md +++ b/spec/EVIDENCE_P13S16_EXECUTION.md @@ -2,11 +2,14 @@ Companion to the §6 report for `spec/CONTRACT_P13S16_PROJECTION.md`. -**Status: review artifact, NOT part of the candidate.** This file is deliberately -**not staged**: it does not appear in the contract's §2 touch table, and gate 4 -requires every staged path to be a §2 row. Including it in the commit would need -its own amendment adding a touch row. It is written here rather than kept in a -temporary directory so the evidence survives the review. +**Status: review artifact. Tracked under `CONTRACT_P13S16_PROJECTION.md` §7's touch +row 12, and NOT part of the rung's candidate.** It documents `aee4ff9`; it is not in it. + +This file was held **untracked** throughout execution and review, because it did not +appear in the contract's §2 touch table and gate 4 requires every staged path to be a §2 +row — so committing it needed an amendment adding one. Amendment 1 added that row, and +the file landed with it. **The distinction survives the change:** the fourteen paths in +`aee4ff9` are the rung; this is the evidence the rung was reviewed against. **Whitespace.** Trailing whitespace has been stripped throughout, so that `git diff --cached --check` passes. It carried no information: it appears only where a