From 3c5f476fa5537c320172f8653e0bbfaf65f20ce8 Mon Sep 17 00:00:00 2001 From: Emil Klein - Claude Code AI Date: Mon, 26 Oct 2026 14:52:25 +0100 Subject: [PATCH 1/8] Session arrival: housekeeping 2026-10-26 (prompt and bootstrap, per DDD-dec-20) Basis: DDD-dec-20 Co-Authored-By: Claude Fable 5.1 --- .../2026-10-26-housekeeping/bootstrap.md | 27 ++++++++ .../2026-10-26-housekeeping/prompt.md | 69 +++++++++++++++++++ meta/sessions/README.md | 1 + 3 files changed, 97 insertions(+) create mode 100644 meta/sessions/2026-10-26-housekeeping/bootstrap.md create mode 100644 meta/sessions/2026-10-26-housekeeping/prompt.md diff --git a/meta/sessions/2026-10-26-housekeeping/bootstrap.md b/meta/sessions/2026-10-26-housekeeping/bootstrap.md new file mode 100644 index 0000000..8348a70 --- /dev/null +++ b/meta/sessions/2026-10-26-housekeeping/bootstrap.md @@ -0,0 +1,27 @@ +# Bootstrap — housekeeping session, 2026-10-26 + +Filled in at arrival and committed with `prompt.md` as the session's first commit. + +| Parameter | Value | +|---|---| +| Invocation | Interactive. Emil asked for a rundown, the proposed list, and recommendations, then ruled "agreed on all execute it". `prompt.md` carries the exchange verbatim | +| Principal | Emil (sole ratifier; ratifies by merging the two pull requests) | +| Upstream repo | github.com/mindovermachine-dev/actor-indexed-determination | +| Upstream base | `1cb3819` — head of `main` at arrival; tag `v5.15.1` points at it | +| Upstream branch | `claude/release-head-guard` | +| Downstream repo | github.com/mindovermachine-dev/decision-driven-design | +| Downstream base | `baec167` — head of `main` at arrival, in sync with `origin/main` | +| Downstream branch | `claude/housekeeping-2026-10-26` | +| Model | Claude Fable 5.1 | +| Gates | None formal. Emil ruled on the charter as a whole; each item lands as its own commit, and the two pull requests are the ratification acts | + +## Scope at arrival + +In scope, from the charter: items 1 to 5 and 8 in full; item 6 for the six org and sim flags. +Deferred by the charter's own sequencing: item 7 (T2b, its own session, after the pin advance to +v5.15.2 completes) and item 6's three address flags (they wait on S-3 and S-4, which are canon +authoring, not housekeeping). S-5 (the Danish glossary rulings) is not taken: ruling Danish terms +is Emil's act, and no release in this session needs it. + +Decision ids: 39 is the next free id across both repositories (upstream holds up to 37, downstream +38). The upstream guard ruling takes 39; the downstream session decision takes 40. diff --git a/meta/sessions/2026-10-26-housekeeping/prompt.md b/meta/sessions/2026-10-26-housekeeping/prompt.md new file mode 100644 index 0000000..698e77c --- /dev/null +++ b/meta/sessions/2026-10-26-housekeeping/prompt.md @@ -0,0 +1,69 @@ +# Prompt — housekeeping session, 2026-10-26 + +The session had no bundled prompt. Its charter is the exchange below, verbatim: Emil's four +messages, and the recommendations Emil agreed to with the fourth. Per `DDD-dec-20`, this file is +committed before any canon edit so the session's scope is fixed at arrival. + +## Emil, message 1 + +> give me a rundown of the canon and what needs accepting + +## Emil, message 2 + +> list all proposed + +## Emil, message 3 + +> give me your recommendations + +## Claude's recommendations (the charter) + +> My recommendation, in the order I would do it. +> +> **1. Strike the Track 1 banners in one housekeeping commit, now.** DDD-dec-27, DDD-dec-28, +> DDD-track-01, the two projection READMEs, the track file, and the five stale pin-group comments +> in `graph/upstream.yaml`. Every one of them records a ratification that already happened. +> Leaving them standing means the repo's own register lies about its state, which is exactly the +> basis-loss the framework warns about. No canon content changes, so it is a ruled edit with +> `Basis: DDD-dec-27; DDD-dec-28`. I can do this today if you say so. +> +> **2. Open a tiny upstream PR for DDD-dec-26 and DDD-frame-02.** Strike the two banners and fix +> the "One / One" duplication. Ship it as v5.15.2, and use it as the first release under the +> release-head guard below. Then the pin advance is a near-zero firing, a good dry run for the +> guard. +> +> **3. Build S-1, the release-head guard, before any other upstream release.** Two consecutive +> releases cut from the wrong head is a class. The remedy is small: an additive `ratified_head` +> field in the release format, and a workflow check that the merge commit's parent matches it. +> Run it against the existing thirteen descriptors first so you know which ones would have +> failed. +> +> **4. Fix S-7 in the same housekeeping pass.** The repo URL still points at the old owner. A +> redirect that lapses fires E12 on all 74 pins at once. One line, one ruling. +> +> **5. Close upstream PR #3 rather than rebase it.** It is eleven weeks stale and rewrites the +> document that establishes the act term. Anything still worth keeping from it should be +> re-proposed against current canon, not merged from a branch that predates seven releases. +> +> **6. Then rule the nine review flags, batched by kind.** The six session-authored org and sim +> claims have no canon document behind them. Either ratify them as projected with a note that the +> exposition is the claim file itself, or demote them to a holding note. They have sat flagged +> since the scaffolding session, and a flag nobody rules on is just noise. The two address-01 +> flags and the address-03 seam-decay flag wait on S-3 and S-4, so file the behaviour term and +> the seam-decay home first, then rule all three together. +> +> **7. Write the T2b pre-registration, S-2, as its own session.** It is the only path that moves +> any address claim out of projected. Hash it before the slice exists, and fold in F-1, the +> escalation-rule anchoring, and the reading/verdict-input line. Do not start it until items 1 +> through 4 are done, so the test runs against a repo whose register is clean. +> +> **8. Decide F-3 explicitly.** It is accepted as proposed but filed nowhere. Either file it as +> DDD-address-06 or record in DDD-address-03's notes that the replication case is excluded by +> design. The fastest clean answer is the second, pending what T2b shows. +> +> What I would leave alone: DDD-dec-14 stays open on purpose, S-8 is low priority by your own +> ruling, and the glossary pass S-5 can ride along with whichever upstream release comes next. + +## Emil, message 4 (the ruling) + +> agreed on all execute it diff --git a/meta/sessions/README.md b/meta/sessions/README.md index f4dd943..5d2ce51 100644 --- a/meta/sessions/README.md +++ b/meta/sessions/README.md @@ -40,3 +40,4 @@ session's later work exceeds the committed prompt, the excess is visible as exce | `2026-09-02-pre-transfer/` | Interactive canon curation — publication readiness before transfer: the accountability arity, the front pages, the pin advance to `v5.13.0`, the readiness report (I-1…I-4) | | `2026-09-27-act-address/` | Interactive design with a pre-registered dry run — the act address: candidate D under test, the layer path and causal time index, occurrence uniqueness (R-1…R-8). **Arrival retroactive**: no prompt was committed before the session ran (`arrival-retroactive.md`, the `DDD-dec-17` precedent); the hashed pre-registration bounds the test, not the design work | | `2026-09-27-act-address-landing/` | Interactive canon curation — lands the act address session in both repositories: `DDD-ground-06`, `term:act-address` and `DDD-dec-37` upstream; `DDD-address-01…05` and `DDD-dec-38` here; the pin advance staged with its firing predicted (gates 0–4) | +| `2026-10-26-housekeeping/` | Housekeeping on Emil's blanket ruling — the Track 1 banners struck in both repositories, the release-head guard (S-1), the `repo:` URL (S-7), upstream PR #3 closed (S-10), the six org/sim review flags ruled, F-3 recorded, and the pin advance to `v5.15.2` staged with its firing predicted | From bd79609bd1c0b6e419357b2432988c67430a653a Mon Sep 17 00:00:00 2001 From: Emil Klein - Claude Code AI Date: Mon, 26 Oct 2026 14:58:18 +0100 Subject: [PATCH 2/8] Strike the Track 1 [PROPOSED] banners: DDD-dec-27, DDD-dec-28, DDD-track-01, the projections tree All ratified by Emil's acceptance of PR #24 (merge e96aa89, 2026-08-18); the banners outlived the ratification by nine weeks. Notes and prose only; no statement, status, region or evidence moves. Basis: DDD-dec-27; DDD-dec-28; DDD-dec-40; DDD-agent-01 Co-Authored-By: Claude Fable 5.1 --- core/claims/DDD-track-01.yaml | 4 +++- core/decisions/DDD-dec-27.yaml | 6 ++++-- core/decisions/DDD-dec-28.yaml | 6 ++++-- projections/README.md | 3 ++- projections/tracks/01-determination.md | 6 ++++-- projections/tracks/README.md | 5 +++-- 6 files changed, 20 insertions(+), 10 deletions(-) diff --git a/core/claims/DDD-track-01.yaml b/core/claims/DDD-track-01.yaml index 471d181..5d17492 100644 --- a/core/claims/DDD-track-01.yaml +++ b/core/claims/DDD-track-01.yaml @@ -32,7 +32,9 @@ test: | owner: none changed: v0.5 (2026-08-18, Track 1 session — filed with the track's rungs 6-10) notes: | - [PROPOSED] Filed at Gate 3 of the Track 1 session. Emil ratifies; nothing here is settled. + Filed at Gate 3 of the Track 1 session and ratified by Emil's acceptance of the Track 1 + pull request (#24, merge e96aa89, 2026-08-18). Ratified means filed, not tested: the claim is projected and nothing here is + settled by the acceptance. The [PROPOSED] banner was struck 2026-10-26 (DDD-dec-40). ## Why this is one claim and not two diff --git a/core/decisions/DDD-dec-27.yaml b/core/decisions/DDD-dec-27.yaml index 840f9b1..0e9136f 100644 --- a/core/decisions/DDD-dec-27.yaml +++ b/core/decisions/DDD-dec-27.yaml @@ -270,8 +270,10 @@ basis: - term:determinable - term:arrangement notes: | - [PROPOSED] Drafted at Gate 2 and committed to the session branch before reporting, per the - session charter. Emil's acceptance is the ratification act. + Ratified. Drafted at Gate 2 and committed to the session branch before reporting, per the + session charter; Emil's acceptance of the Track 1 pull request (#24, merge e96aa89, 2026-08-18) + was the ratification act. The [PROPOSED] banner outlived it by nine weeks and was + struck 2026-10-26 on Emil's ruling at the housekeeping session (DDD-dec-40). Numbering: decisions share one id space across the principle repo and this one. 26 is the upstream session decision; 27 is this one. diff --git a/core/decisions/DDD-dec-28.yaml b/core/decisions/DDD-dec-28.yaml index d543d65..1695cde 100644 --- a/core/decisions/DDD-dec-28.yaml +++ b/core/decisions/DDD-dec-28.yaml @@ -6,7 +6,7 @@ statement: | principal: Emil made: 2026-08-18, Track 1 session (post-merge; upstream PR #15 merged as 9e92099, tagged v5.8.0) resolution: | - [PROPOSED] The advance, and what it fired. + The advance, and what it fired. ## The advance @@ -62,7 +62,9 @@ basis: - DDD-agent-01 - DDD-frame-02 notes: | - [PROPOSED] Filed at the post-merge step of the Track 1 session. Emil ratifies. + Filed at the post-merge step of the Track 1 session and ratified by Emil's acceptance of the + Track 1 pull request (#24, merge e96aa89, 2026-08-18). The [PROPOSED] banners in resolution and notes were struck + 2026-10-26 (DDD-dec-40). Numbering: decisions share one id space across the principle repo and this one. 26 was the upstream session decision, 27 this session's downstream decision, 28 this advance. diff --git a/projections/README.md b/projections/README.md index b5b5371..24098f6 100644 --- a/projections/README.md +++ b/projections/README.md @@ -4,7 +4,8 @@ layers `meta/way-of-working.md` §1 names — framework (canon, upstream), program (`meta/`), projections (here). -**[PROPOSED] This tree is new as of 2026-08-18** (`DDD-dec-27`). It was prescribed by +**This tree is new as of 2026-08-18** (`DDD-dec-27`, ratified; its `[PROPOSED]` banner struck +2026-10-26 under `DDD-dec-40`). It was prescribed by `meta/way-of-working.md` §1 and written out in §5's repo-structure block from the beginning, and stood unbuilt through the split; the determination learning track is the first artifact that had nowhere else to live. Creating the directory realises the specification rather than extending it. diff --git a/projections/tracks/01-determination.md b/projections/tracks/01-determination.md index 3b70072..9de3a39 100644 --- a/projections/tracks/01-determination.md +++ b/projections/tracks/01-determination.md @@ -4,8 +4,10 @@ constant while the words change.** Ten rungs. For software engineers; C#/.NET fluency assumed, framework vocabulary assumed absent. -> **[PROPOSED] — all ten rungs drafted, Gate 3, 2026-08-18.** Nothing here is ratified. Emil -> merges and ratifies; this document proposes. +> **Ratified.** All ten rungs were drafted at Gate 3, 2026-08-18, and accepted by Emil's merge of +> pull request #24 (e96aa89). +> The `[PROPOSED]` banner that stood here was struck 2026-10-26 (`DDD-dec-40`). Ratified means +> filed, not tested: the track's claim, `DDD-track-01`, is projected. --- diff --git a/projections/tracks/README.md b/projections/tracks/README.md index f08aa52..e209614 100644 --- a/projections/tracks/README.md +++ b/projections/tracks/README.md @@ -4,7 +4,8 @@ worked decision that does not change.** A track is a projection like any other: filtered, re-registered, pinned, manifested. -**[PROPOSED]** — 2026-08-18, `DDD-dec-27`. Emil ratifies. +Filed 2026-08-18 under `DDD-dec-27` and ratified by Emil's acceptance; the `[PROPOSED]` banner +that stood here was struck 2026-10-26 (`DDD-dec-40`). ## What a track is @@ -61,4 +62,4 @@ canon and what would change that. | Track | Vocabulary | Worked decision | Status | |---|---|---|---| -| `01-determination.md` | determinable, determinate, ground, actor, arrangement, commitment level, residual discretion, closure, assurance, escape, accountability | retry count, rungs 1–9; transcript retention period, rung 10 | **[PROPOSED]** — all ten rungs drafted; claim `DDD-track-01` | +| `01-determination.md` | determinable, determinate, ground, actor, arrangement, commitment level, residual discretion, closure, assurance, escape, accountability | retry count, rungs 1–9; transcript retention period, rung 10 | Ratified (PR #24, 2026-08-18); claim `DDD-track-01`, projected | From d5760402a7a19c5e0dc15cfc16d9113a3ba1bbef Mon Sep 17 00:00:00 2001 From: Emil Klein - Claude Code AI Date: Mon, 26 Oct 2026 14:58:19 +0100 Subject: [PATCH 3/8] graph: repo URL to mindovermachine-dev (S-7); five stale [PROPOSED] pin-group markers struck Basis: DDD-dec-40; DDD-dec-27; DDD-dec-28; DDD-dec-34; DDD-dec-38; DDD-agent-01 Co-Authored-By: Claude Fable 5.1 --- graph/upstream.yaml | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/graph/upstream.yaml b/graph/upstream.yaml index 292033c..4db1dfb 100644 --- a/graph/upstream.yaml +++ b/graph/upstream.yaml @@ -14,7 +14,10 @@ format: upstream/v1 upstream: - repo: https://github.com/Hafeok/actor-indexed-determination + # The repo moved to the mindovermachine-dev organisation at the transfer (2026-09). Until + # 2026-10-26 this line still named the old owner and resolved through GitHub's redirect; a + # redirect that lapses fires E12 on every pin at once. Changed by ruling (DDD-dec-40, S-7). + repo: https://github.com/mindovermachine-dev/actor-indexed-determination # Advanced v5.0.0 -> v5.2.0 on Emil's upstream acceptance (merge e86fd23, tagged v5.2.0); # the advance is recorded in core/decisions/DDD-dec-10. # Advanced v5.2.0 -> v5.3.0 on Emil's upstream acceptance of the Wave 2 PR (merge 1db6772, @@ -117,6 +120,9 @@ upstream: # in every limb. After re-instrumenting DDD-frame-08: 74 pins, 0 basis-loss, 0 content-drift, # 1 shadowed id. ref: v5.15.1 # tag, never a branch + # Five pin batches below carried a "[PROPOSED]" marker on their group comment. Each batch's + # decision is filed and ratified (DDD-dec-27, -28, -34, -38); the markers were struck + # 2026-10-26 (DDD-dec-40). The comments keep their dated reasoning. pins: # basis claims for DDD-dec-04 (the split decision itself rests on these) - id: DDD-frame-01 @@ -241,7 +247,7 @@ upstream: - id: DDD-hyp-05 status_at_pin: projected content_hash: sha256:115bdd9e449d3929de9a96323e355503b950de3e001252e6dc0627bd7f041251 - # [PROPOSED] Track 1 additions (2026-08-18, DDD-dec-27): the ids the determination track + # Track 1 additions (2026-08-18, DDD-dec-27): the ids the determination track # cites by ddd:ref in projections/tracks/01-determination.md. Pins added at the SAME ref # (v5.7.0) — no advance is proposed here, and none of these ids moved at Wave 3. Added # because W5 fires on a ddd:ref to an unpinned id anywhere under the repo root: a track @@ -293,7 +299,7 @@ upstream: - id: DDD-frame-13 status_at_pin: projected content_hash: sha256:4add58e0f47c0ff22bb752d6b78aef7f591a14b17d610cdb06677439e0b33276 - # [PROPOSED] Track 1, Gate 3 additions (2026-08-18, DDD-dec-27): the ids rungs 6-10 cite by + # Track 1, Gate 3 additions (2026-08-18, DDD-dec-27): the ids rungs 6-10 cite by # ddd:ref, plus DDD-frame-08 for rung 4's accountable-principal row (flagged at Gate 2 as # stated without a citation; the citation is the fix). Same ref (v5.7.0), no advance. - id: DDD-frame-08 @@ -344,7 +350,7 @@ upstream: - id: DDD-ground-04 status_at_pin: projected content_hash: sha256:36081b0a401d947f8b317b87bdc6879793c3a4476bfe0cdbe9bd3f2df6e4dd09 - # [PROPOSED] The v5.8.0 mints (DDD-dec-28). Deliberately absent from the Gate 2/3 pin + # The v5.8.0 mints (DDD-dec-28). Deliberately absent from the Gate 2/3 pin # batches: they do not exist at v5.7.0, and pinning them there would have fired E12. - id: term:commitment-level status_at_pin: draft @@ -352,7 +358,7 @@ upstream: - id: term:residual-discretion status_at_pin: draft content_hash: sha256:9bbe31e3a02fd3cee70ad42d560268943cd136aa1c0d389ec081d7af0c579340 - # [PROPOSED] Paper A revision (2026-08-30), added at the v5.12.0 advance. Four nodes the + # Paper A revision (2026-08-30), added at the v5.12.0 advance. Four nodes the # manuscript leans on that were NOT pinned, found by the Gate 1 status sweep rather than by # the instrument: DDD-measure-06 retires at v5.12.0 and fired NOTHING, because W5 only sees # ids that are pinned. The paper asserted it as **established** in three places and both @@ -373,7 +379,7 @@ upstream: - id: DDD-measure-17 status_at_pin: projected content_hash: sha256:164a18072145bc4a0cdb3c6e1ca8890fc64c1b36396c73be5ca8bd45c66114e5 - # [PROPOSED] Act address landing (2026-09-28, DDD-dec-38), staged with the v5.15.0 advance. + # Act address landing (2026-09-28, DDD-dec-38), staged with the v5.15.0 advance. # DDD-ground-06 and term:act-address are the basis of DDD-address-01..05; they do not exist # before v5.15.0, so pinning them earlier would fire E12. DDD-ground-01 is DDD-dec-38's # basis and was unpinned (DDD-agent-01). Hashes taken at upstream cc0abf8. From 9d57361532066960db21b669182371d22fca1b60 Mon Sep 17 00:00:00 2001 From: Emil Klein - Claude Code AI Date: Mon, 26 Oct 2026 14:58:20 +0100 Subject: [PATCH 4/8] Rule the six org/sim review flags as projected; record the F-3 ruling in DDD-address-03 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit DDD-org-01..04, DDD-sim-01, DDD-sim-02: the session-authored flag standing since v4.5 is replaced by the ruling — ratified as projected, the claim file is the exposition, no prose document is owed. DDD-address-03: F-3 (the replication case) stays excluded by design, provisional on T2b. Basis: DDD-dec-40; DDD-org-01; DDD-org-02; DDD-org-03; DDD-org-04; DDD-sim-01; DDD-sim-02; DDD-address-03 Co-Authored-By: Claude Fable 5.1 --- core/claims/DDD-address-03.yaml | 7 +++++++ core/claims/DDD-org-01.yaml | 2 +- core/claims/DDD-org-02.yaml | 2 +- core/claims/DDD-org-03.yaml | 2 +- core/claims/DDD-org-04.yaml | 2 +- core/claims/DDD-sim-01.yaml | 2 +- core/claims/DDD-sim-02.yaml | 2 +- 7 files changed, 13 insertions(+), 6 deletions(-) diff --git a/core/claims/DDD-address-03.yaml b/core/claims/DDD-address-03.yaml index 562e9e8..3595de1 100644 --- a/core/claims/DDD-address-03.yaml +++ b/core/claims/DDD-address-03.yaml @@ -27,3 +27,10 @@ notes: | at 361e88f / cba63ef. Filed with the reliance carried as a successor item (GATE 1 ruling 6). Only the notes and the "pricing of reuse as seam risk" limb of breaks lean on it; the statement does not. No other claim is cited as support for it. + + F-3, ruled 2026-10-26 (DDD-dec-40). The dry-run finding accepted as [PROPOSED] at the landing + session's GATE 1 — where occurrences replicate a decision instead of sharing a component, the + fan-out is the decision's predicate match set — stays excluded from this claim by design, as the + region already records, and is not filed as a sixth address claim. The ruling is provisional on + T2b (successor item S-2): if the slice shows the replication case carrying the same escape + shape, it is filed then, with T2b's evidence, rather than now without it. diff --git a/core/claims/DDD-org-01.yaml b/core/claims/DDD-org-01.yaml index 73b1256..d60be7b 100644 --- a/core/claims/DDD-org-01.yaml +++ b/core/claims/DDD-org-01.yaml @@ -11,4 +11,4 @@ falsifier: | owner: none changed: v4.5 notes: | - UNVERIFIED — session-authored; Emil review. The org-design projection is parked per meta/way-of-working §4; no core/ or meta/ document states this predictive claim. The underlying primitives (status floors, manifests, single-canon correction flow) are canon (meta/way-of-working §§2-3), but the organisational-outcome prediction is not. + Ruled 2026-10-26 (DDD-dec-40): ratified as projected; this file is the claim's exposition, no core/ or meta/ prose document states it, and none is owed. Session-authored. The org-design projection is parked per meta/way-of-working §4; no core/ or meta/ document states this predictive claim. The underlying primitives (status floors, manifests, single-canon correction flow) are canon (meta/way-of-working §§2-3), but the organisational-outcome prediction is not. diff --git a/core/claims/DDD-org-02.yaml b/core/claims/DDD-org-02.yaml index 7307922..771c180 100644 --- a/core/claims/DDD-org-02.yaml +++ b/core/claims/DDD-org-02.yaml @@ -15,4 +15,4 @@ breaks: >- owner: none changed: v4.5 notes: | - UNVERIFIED — session-authored; Emil review. The Martin SDP credit is genuine canon prior art (meta/lineage-and-limits §1.12), but the statused-SDP organisational prediction here is session-authored and stated in no core/ or meta/ document. + Ruled 2026-10-26 (DDD-dec-40): ratified as projected; this file is the claim's exposition, no core/ or meta/ prose document states it, and none is owed. Session-authored. The Martin SDP credit is genuine canon prior art (meta/lineage-and-limits §1.12), but the statused-SDP organisational prediction here is session-authored and stated in no core/ or meta/ document. diff --git a/core/claims/DDD-org-03.yaml b/core/claims/DDD-org-03.yaml index 357e939..7b65efa 100644 --- a/core/claims/DDD-org-03.yaml +++ b/core/claims/DDD-org-03.yaml @@ -15,4 +15,4 @@ breaks: | owner: none changed: v4.5 notes: | - UNVERIFIED — session-authored; Emil review. Reinertsen is canon prior art (meta/lineage-and-limits); the PO-as-seam / governed-priority prediction is session-authored and stated in no canon document. Depends on the commitment-level vocabulary that DDD-frame-02 also flags as not-yet-in-core/. + Ruled 2026-10-26 (DDD-dec-40): ratified as projected; this file is the claim's exposition, no core/ or meta/ prose document states it, and none is owed. Session-authored. Reinertsen is canon prior art (meta/lineage-and-limits); the PO-as-seam / governed-priority prediction is session-authored and stated in no canon document. Depends on the commitment-level vocabulary that DDD-frame-02 also flags as not-yet-in-core/. diff --git a/core/claims/DDD-org-04.yaml b/core/claims/DDD-org-04.yaml index 104ce35..f71eb7e 100644 --- a/core/claims/DDD-org-04.yaml +++ b/core/claims/DDD-org-04.yaml @@ -16,4 +16,4 @@ breaks: | owner: none changed: v4.5 notes: | - UNVERIFIED — session-authored; Emil review. Cross-domain retrodiction; no core/ or meta/ document states it. The reversal-cost/feedback-latency parameters are framework concepts (core/03, applications/sdlc) but their cross-industry predictive use is session-authored. + Ruled 2026-10-26 (DDD-dec-40): ratified as projected; this file is the claim's exposition, no core/ or meta/ prose document states it, and none is owed. Session-authored. Cross-domain retrodiction; no core/ or meta/ document states it. The reversal-cost/feedback-latency parameters are framework concepts (core/03, applications/sdlc) but their cross-industry predictive use is session-authored. diff --git a/core/claims/DDD-sim-01.yaml b/core/claims/DDD-sim-01.yaml index 495d269..e96c8ce 100644 --- a/core/claims/DDD-sim-01.yaml +++ b/core/claims/DDD-sim-01.yaml @@ -15,4 +15,4 @@ breaks: | owner: none changed: v4.5 notes: | - UNVERIFIED — session-authored; Emil review. Cascade-prediction model stated in no canon document; sequenced after the tool logs ≥1 real revision cycle, so unexercisable now. Credits (Hawkes, PERT Monte Carlo, dependency-cascade models) are genuine prior art but the statused-claim-graph substrate is the session's proposal. Value-of-information corollary: expected fragility reduction per claim tested ranks which claim the next paper should pay; converts DDD-org-01 from retrospective to prospective if it holds. + Ruled 2026-10-26 (DDD-dec-40): ratified as projected; this file is the claim's exposition, no core/ or meta/ prose document states it, and none is owed. Session-authored. Cascade-prediction model stated in no canon document; sequenced after the tool logs ≥1 real revision cycle, so unexercisable now. Credits (Hawkes, PERT Monte Carlo, dependency-cascade models) are genuine prior art but the statused-claim-graph substrate is the session's proposal. Value-of-information corollary: expected fragility reduction per claim tested ranks which claim the next paper should pay; converts DDD-org-01 from retrospective to prospective if it holds. diff --git a/core/claims/DDD-sim-02.yaml b/core/claims/DDD-sim-02.yaml index 83588c2..4727732 100644 --- a/core/claims/DDD-sim-02.yaml +++ b/core/claims/DDD-sim-02.yaml @@ -13,4 +13,4 @@ breaks: nothing downstream — DDD-sim-01 stands independently owner: none changed: v4.5 notes: | - UNVERIFIED — session-authored; Emil review. Growth-prediction model stated in no canon document; explicitly weaker than DDD-sim-01 and statused separately. + Ruled 2026-10-26 (DDD-dec-40): ratified as projected; this file is the claim's exposition, no core/ or meta/ prose document states it, and none is owed. Session-authored. Growth-prediction model stated in no canon document; explicitly weaker than DDD-sim-01 and statused separately. From dbabbce10f8208dd91f70a891947bf6f12c39e9a Mon Sep 17 00:00:00 2001 From: Emil Klein - Claude Code AI Date: Mon, 26 Oct 2026 14:58:49 +0100 Subject: [PATCH 5/8] Pin advance v5.15.1 -> v5.15.2: the firing predicted before the ref moves (0/0/0/0/W7 1) Basis: DDD-dec-40; DDD-dec-38; DDD-agent-01 Co-Authored-By: Claude Fable 5.1 --- .../pin-advance-prediction.md | 44 +++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 meta/sessions/2026-10-26-housekeeping/pin-advance-prediction.md diff --git a/meta/sessions/2026-10-26-housekeeping/pin-advance-prediction.md b/meta/sessions/2026-10-26-housekeeping/pin-advance-prediction.md new file mode 100644 index 0000000..c8d3a84 --- /dev/null +++ b/meta/sessions/2026-10-26-housekeeping/pin-advance-prediction.md @@ -0,0 +1,44 @@ +# Predicted firing of the pin advance v5.15.1 → v5.15.2 (housekeeping session) + +**Written and committed before the ref moves.** The staging commit that follows, and the bump on +Emil's acceptance of upstream PR #26, are the operation. Verification compares the observed firing +with this file limb by limb and records any divergence rather than reconciling it. + +## The advance + +| | Value | +|---|---| +| From | `v5.15.1` (the pin at `baec167`) | +| Staged at | upstream branch `claude/release-head-guard`, head `630475c` (PR #26) | +| To, on acceptance | tag `v5.15.2`, cut when PR #26 merges, under the release-head guard | +| Releases crossed | v5.15.2 only | +| Pins before | 74 | +| Pins added | 0 | +| Pins after | 74 | + +## Prediction, limb by limb + +| Limb | Predicted | Why | +|---|---|---| +| **E12** | **0** | PR #26 adds, removes and renames no claim or term. | +| **E13** | **0** | No `canonical_md` moves; nothing embedded here changes. | +| **W5** | **0** | No pinned status moves. `DDD-frame-02` stays projected; `DDD-dec-26` is a decision and is not pinned. | +| **W6** | **0** | The two canon edits in PR #26 are notes-only (`DDD-frame-02` notes; `DDD-dec-26` notes). Notes are outside the three fields `pinned_content_digest` hashes (statement, region, `canonical_md`). `DDD-frame-02`'s pinned digest `sha256:0002f60b…` is predicted unchanged. | +| **W7** | **1, unchanged** | The one standing shadowed id. | + +Summary line expected from the checker at the staged ref and at the tag alike: **74 pins resolved, +0 basis-loss, 0 content-drift, 1 shadowed id**. No re-instrumentation step follows, because no +hash moves. This is the near-zero firing the charter asked for as the guard's dry run: the guard's +first release is one whose downstream consequence is predicted at nothing, so any firing at all is +a finding. + +## Conditions that void this prediction + +- **PR #26 changes before merge in a hashed field.** A ruled change to `DDD-frame-02`'s statement + or region, or to any pinned term's `canonical_md`, voids the W6 limb; the prediction is restated + in a new commit to this directory before the bump. Notes-only changes do not. +- **Another release lands first.** If any upstream release is cut between `v5.15.1` and + `v5.15.2`, the prediction is re-run against it before the bump. +- **The guard refuses the cut.** If `v5.15.2`'s descriptor fails rule 7 at the merge (the head + moved), no tag exists to bump to; the fix is a new descriptor commit upstream, and this + prediction stands unchanged, since the canon it predicts over is unchanged. From 527076d5726251238aa8dc0ebc8bebfe1622e790 Mon Sep 17 00:00:00 2001 From: Emil Klein - Claude Code AI Date: Mon, 26 Oct 2026 15:00:02 +0100 Subject: [PATCH 6/8] Stage the upstream pin v5.15.1 -> v5.15.2 against claude/release-head-guard (not bumped) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ref -> claude/release-head-guard (upstream PR #26), per the DDD-dec-10/16/18/25/28/38 pattern; no pins added, none removed. Staged preview, after the prediction commit dbabbce: 74 pins resolved, 0 basis-loss, 0 content-drift, 1 shadowed id — every limb as predicted. Preview, not verification: the verification of record is against the tag. Basis: DDD-dec-40; DDD-dec-39; DDD-dec-38; DDD-dec-10 Co-Authored-By: Claude Fable 5.1 --- graph/upstream.yaml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/graph/upstream.yaml b/graph/upstream.yaml index 4db1dfb..b177ea5 100644 --- a/graph/upstream.yaml +++ b/graph/upstream.yaml @@ -119,7 +119,14 @@ upstream: # DDD-frame-08, both digests as written down beforehand — 1 shadowed id. The prediction held # in every limb. After re-instrumenting DDD-frame-08: 74 pins, 0 basis-loss, 0 content-drift, # 1 shadowed id. - ref: v5.15.1 # tag, never a branch + # Advancing v5.15.1 -> v5.15.2 at the housekeeping session (2026-10-26), staged against the + # upstream branch per the DDD-dec-10/16/18/25/28/38 pattern; the advance is DDD-dec-40 here, + # DDD-dec-39 upstream. v5.15.2 is the first release cut under the release-head guard (S-1). + # Predicted firing, committed before this line moved + # (meta/sessions/2026-10-26-housekeeping/pin-advance-prediction.md): E12 0 - E13 0 - W5 0 - + # W6 0 - W7 1, unchanged. PR #26's two canon edits are notes-only, outside the hashed fields. + # No pins added, none removed. + ref: claude/release-head-guard # staged; bumps to tag v5.15.2 on acceptance of upstream PR #26 # Five pin batches below carried a "[PROPOSED]" marker on their group comment. Each batch's # decision is filed and ratified (DDD-dec-27, -28, -34, -38); the markers were struck # 2026-10-26 (DDD-dec-40). The comments keep their dated reasoning. From 82b871d3de1ca6e844220e529180791a80a44d5b Mon Sep 17 00:00:00 2001 From: Emil Klein - Claude Code AI Date: Mon, 26 Oct 2026 15:00:03 +0100 Subject: [PATCH 7/8] DDD-dec-40: the housekeeping ruling; session close record and successor items Basis: DDD-dec-40; DDD-dec-39; DDD-dec-38; DDD-dec-27; DDD-dec-28; DDD-agent-01 Co-Authored-By: Claude Fable 5.1 --- core/decisions/DDD-dec-40.yaml | 88 +++++++++++++++++++ .../2026-10-26-housekeeping/bootstrap.md | 10 +++ .../successor-items.md | 25 ++++++ 3 files changed, 123 insertions(+) create mode 100644 core/decisions/DDD-dec-40.yaml create mode 100644 meta/sessions/2026-10-26-housekeeping/successor-items.md diff --git a/core/decisions/DDD-dec-40.yaml b/core/decisions/DDD-dec-40.yaml new file mode 100644 index 0000000..935eac6 --- /dev/null +++ b/core/decisions/DDD-dec-40.yaml @@ -0,0 +1,88 @@ +format: 1 +id: DDD-dec-40 +kind: decision +statement: | + The housekeeping ruling of 2026-10-26: every ratification banner that outlived its ratification is struck in both repositories; the upstream repo URL names its current owner; the six session-authored org and sim claims are ratified as projected with the claim file as their exposition; F-3 stays excluded from DDD-address-03 by design, provisional on T2b; stale upstream PR #3 is closed; and the upstream pin advances v5.15.1 -> v5.15.2, the first release cut under the release-head guard, with its firing predicted at nothing. +principal: Emil +made: 2026-10-26, housekeeping session; ruled as a whole ("agreed on all execute it") on the recommendations committed verbatim at meta/sessions/2026-10-26-housekeeping/prompt.md; Emil's acceptance of the downstream pull request is the ratification act, and the pin bumps to the tag on acceptance of upstream PR #26 +resolution: | + ## What the rundown found + + Both repositories were clean and in sync at the pinned tag v5.15.1. No pull request was + open downstream; upstream held one, PR #3, stale since 2026-08-06 and conflicting. All 31 + downstream claims but one were projected. What was waiting on Emil was rulings, not merges: + nine review flags, ten successor items from the act address landing, and a set of [PROPOSED] + banners whose ratification had already happened. The banners were the finding: every one of + them recorded a ratification act (PR #24 downstream, PR #15 upstream, 2026-08-18) that was + nine weeks old, and two sessions had booked them as freight and left them shut. + + ## Rulings, by charter item + + 1. **Track 1 banners struck, downstream.** DDD-dec-27, DDD-dec-28, DDD-track-01, + projections/README.md, projections/tracks/README.md, projections/tracks/01-determination.md, + and the five pin-group markers in graph/upstream.yaml. Each now records the ratification + (PR #24, merge e96aa89) and the strike. Notes and prose only; nothing hashed moves. + 2. **Track 1 banners struck, upstream.** DDD-dec-26 and DDD-frame-02, with DDD-frame-02's + duplicated word, in upstream PR #26, which proposes v5.15.2 (DDD-dec-39). + 3. **The release-head guard, S-1.** Ruled and built upstream as DDD-dec-39: format 2 of the + release format, mandatory ratified_head, rule 7, the checker, both workflow hooks, and the + hit-list run before the class was chosen — both recorded misses fire, both controls pass. + v5.15.2 is its first instance. + 4. **The repo URL, S-7.** graph/upstream.yaml names mindovermachine-dev. The old owner resolved + through a redirect; a redirect that lapses fires E12 on all 74 pins at once. Verified: the + checker resolves 74 pins through the new URL with nothing fired. + 5. **Upstream PR #3 closed, S-10.** Closed with the ruling recorded in its comment and the + branch left in place. Anything still worth keeping is re-proposed against current canon. + 6. **The six org/sim review flags.** DDD-org-01..04, DDD-sim-01, DDD-sim-02 carried + "UNVERIFIED — session-authored; Emil review" since v4.5. Ruled: ratified as projected; the + claim file is the claim's exposition; no core/ or meta/ prose document states them and none + is owed. The ruling changes no status and adds no evidence: a projected claim nobody has + tested is exactly what the status says. The three address flags (DDD-address-01 twice, + DDD-address-03 once) are NOT ruled here: they wait on S-3 and S-4, which are canon + authoring, and are ruled together when those land. + 7. **T2b, S-2.** Not started, by the charter's own sequencing: its own session, after this + advance completes, so the test runs against a repository whose register is clean. + 8. **F-3.** The replication case stays excluded from DDD-address-03 by design, as its region + already records, and is not filed as a sixth address claim. Provisional on T2b: if the slice + shows the replication case carrying the same escape shape, it is filed then with evidence. + + ## The pin advance + + Staged against upstream branch claude/release-head-guard per the DDD-dec-10/16/18/25/28/38 + pattern, with the prediction committed first (pin-advance-prediction.md, dbabbce): E12 0 - + E13 0 - W5 0 - W6 0 - W7 1, unchanged, because PR #26's two canon edits are notes-only and + notes are outside the hashed fields. Staged preview at the branch: 74 pins resolved, + 0 basis-loss, 0 content-drift, 1 shadowed id — every limb as predicted. The verification of + record is against the tag, on acceptance; the bump is the one act this session leaves open. + + This is the first advance whose upstream release is guarded. If the guard refuses the cut + because the head moved, no tag exists to bump to, the fix is a new descriptor commit upstream, + and this prediction stands, since the canon it predicts over is unchanged. + + ## Why banners are basis loss and not tidiness + + A [PROPOSED] marker on a ratified object is a false statement of the object's status in the + file that governs it. A reader querying the file — which is what basis-as-query means — gets + "not ratified" back for an object the principal ratified nine weeks earlier. Two sessions saw + it and deferred it, which is how a false status becomes a standing one. The release misses + that S-1 remedies are the same shape in the other direction: there the record said less than + the world, here it said more. +basedOn: + - DDD-dec-39 + - DDD-dec-38 + - DDD-dec-27 + - DDD-dec-28 + - DDD-agent-01 +notes: | + Filed from the housekeeping session (meta/sessions/2026-10-26-housekeeping/, arrival per + DDD-dec-20). Decision ids share one space across the two repositories: 39 is the upstream + ruling in the same session, 40 this one. + + Not done, and why: S-5 (the Danish glossary rulings) is Emil's act and nothing here needs it; + S-8 (decision pinning) is low priority by Emil's ruling at the landing session and this + decision's basedOn DDD-dec-39 is, like DDD-dec-38's DDD-dec-37, an unpinned upstream decision; + S-3, S-4, S-6 and S-9 are canon authoring and are carried forward unchanged. + + On closing this session, the bump: on Emil's acceptance of upstream PR #26, ref moves from the + branch to the tag v5.15.2, the checker is run with the hashes untouched so the zero firing is + observed rather than assumed, and the observation is recorded here as the verification. diff --git a/meta/sessions/2026-10-26-housekeeping/bootstrap.md b/meta/sessions/2026-10-26-housekeeping/bootstrap.md index 8348a70..5e6cb6a 100644 --- a/meta/sessions/2026-10-26-housekeeping/bootstrap.md +++ b/meta/sessions/2026-10-26-housekeeping/bootstrap.md @@ -25,3 +25,13 @@ is Emil's act, and no release in this session needs it. Decision ids: 39 is the next free id across both repositories (upstream holds up to 37, downstream 38). The upstream guard ruling takes 39; the downstream session decision takes 40. + +## Session record + +| File | What | +|---|---| +| `prompt.md` | The charter, verbatim | +| `pin-advance-prediction.md` | The firing predicted before the ref moved (`dbabbce`) | +| `successor-items.md` | S-1, S-7, S-10 closed; S-2..S-6, S-8, S-9 carried; H-1..H-3 new | +| `core/decisions/DDD-dec-40.yaml` | The ruling, and the open bump | +| Upstream PR #26 | `DDD-dec-39`, the guard, the banners, `v5.15.2` proposed | diff --git a/meta/sessions/2026-10-26-housekeeping/successor-items.md b/meta/sessions/2026-10-26-housekeeping/successor-items.md new file mode 100644 index 0000000..99b090d --- /dev/null +++ b/meta/sessions/2026-10-26-housekeeping/successor-items.md @@ -0,0 +1,25 @@ +# Successor items — housekeeping session, 2026-10-26 + +Carried forward from the act address landing's list, renumbered nowhere: the S-numbers are the +landing session's and stay stable. Items this session closed are marked; the rest are `[OPEN]`. + +| # | Item | State after this session | +|---|---|---| +| S-1 | Release-head guard | **Closed.** Built upstream as `DDD-dec-39` (format 2, `ratified_head`, rule 7, `scripts/check-release-head.py`, both workflow hooks). First instance: `v5.15.2`. | +| S-2 | T2b, the first Phoenix slice | `[OPEN]`. Its own session, after the bump to `v5.15.2`. Carries F-1, the escalation-rule anchoring, the reading/verdict-input line. The address flags and F-3's provisional ruling wait on it. | +| S-3 | Seam decay's canonical home | `[OPEN]`. Unchanged. `DDD-address-03`'s flag waits on it. | +| S-4 | The behaviour term | `[OPEN]`. Unchanged. `DDD-address-05`'s dependency and `DDD-address-01`'s K5 rationale wait on it. | +| S-5 | Glossary pass (act, act occurrence, act-site, ground axis) | `[OPEN]`. Not taken: Emil's act, and no release this session needed it. Rides with the next upstream release that touches the glossary. | +| S-6 | Held dry-run findings F-1, F-2 | `[OPEN]`. F-1 carried into S-2; F-2 ruled after T2b. | +| S-7 | The `repo:` URL | **Closed.** `graph/upstream.yaml` names `mindovermachine-dev`; 74 pins verified through the new URL. | +| S-8 | Decision pinning for `basedOn` | `[OPEN]`. Low priority, unchanged. `DDD-dec-40`'s basedOn `DDD-dec-39` is the third unpinned upstream decision reference. | +| S-9 | The `term:act` relation in `DDD-ground-06` | `[OPEN]`. Unchanged. | +| S-10 | Stale upstream PR #3 | **Closed.** Closed 2026-10-26 with the ruling in its comment; branch left in place. | + +New this session: + +| # | Item | What it needs | +|---|---|---| +| H-1 | **The bump.** `graph/upstream.yaml` is staged at `claude/release-head-guard`. | On Emil's acceptance of upstream PR #26: ref → `v5.15.2`, checker run with hashes untouched, observation recorded in `DDD-dec-40` against `pin-advance-prediction.md`. | +| H-2 | **The three address review flags.** `DDD-address-01` (two), `DDD-address-03` (one). | Ruled together when S-3 and S-4 land. | +| H-3 | **The org-03 / org-04 two-limb warnings.** The validator flags both statements as joining two limbs. | Adjudicate (split or keep) at the next canon session that touches the org set; not a housekeeping edit, since a split mints an id. | From 8dbf2297c4655f13850ac867289c8003bd301308 Mon Sep 17 00:00:00 2001 From: Emil Klein - Claude Code AI Date: Mon, 26 Oct 2026 15:04:22 +0100 Subject: [PATCH 8/8] Pin advance v5.15.1 -> v5.15.2 verified: ref to the tag, hashes untouched, firing as predicted (0/0/0/0/W7 1) v5.15.2 was cut under the release-head guard (first live pass: ratified_head 0849ab8, second parent 630475c, descriptor only). Ref advanced alone; the checker observed 74 pins, 0 basis-loss, 0 content-drift, 1 shadowed id, as predicted at dbabbce. Nothing to re-instrument. H-1 closes. Basis: DDD-dec-40; DDD-dec-39; DDD-dec-38; DDD-agent-01 Co-Authored-By: Claude Fable 5.1 --- core/decisions/DDD-dec-40.yaml | 13 ++++++++++--- graph/upstream.yaml | 8 ++++++-- .../2026-10-26-housekeeping/successor-items.md | 2 +- 3 files changed, 17 insertions(+), 6 deletions(-) diff --git a/core/decisions/DDD-dec-40.yaml b/core/decisions/DDD-dec-40.yaml index 935eac6..f4cf69e 100644 --- a/core/decisions/DDD-dec-40.yaml +++ b/core/decisions/DDD-dec-40.yaml @@ -83,6 +83,13 @@ notes: | decision's basedOn DDD-dec-39 is, like DDD-dec-38's DDD-dec-37, an unpinned upstream decision; S-3, S-4, S-6 and S-9 are canon authoring and are carried forward unchanged. - On closing this session, the bump: on Emil's acceptance of upstream PR #26, ref moves from the - branch to the tag v5.15.2, the checker is run with the hashes untouched so the zero firing is - observed rather than assumed, and the observation is recorded here as the verification. + The bump, verified. Emil accepted upstream PR #26 (merge 084bce7, 2026-10-26); the release + workflow cut v5.15.2 with the guard's gate passing at the cut — ratified_head 0849ab8, merge's + second parent 630475c, nothing but the descriptor between them — the guard's first live pass. + Ref advanced from the branch to the tag with the hashes untouched, so a firing would have been + observed rather than assumed: + + PREDICTED E12 0 - E13 0 - W5 0 - W6 0 - W7 1, unchanged + OBSERVED 74 pins resolved against the pinned ref, 0 basis-loss, 0 content-drift, 1 shadowed id(s); 0 errors, 0 warnings + + The prediction held in every limb. Nothing to re-instrument. H-1 closes. diff --git a/graph/upstream.yaml b/graph/upstream.yaml index b177ea5..58438f0 100644 --- a/graph/upstream.yaml +++ b/graph/upstream.yaml @@ -125,8 +125,12 @@ upstream: # Predicted firing, committed before this line moved # (meta/sessions/2026-10-26-housekeeping/pin-advance-prediction.md): E12 0 - E13 0 - W5 0 - # W6 0 - W7 1, unchanged. PR #26's two canon edits are notes-only, outside the hashed fields. - # No pins added, none removed. - ref: claude/release-head-guard # staged; bumps to tag v5.15.2 on acceptance of upstream PR #26 + # No pins added, none removed. Verified at the bump (PR #26 merged 084bce7, tagged v5.15.2 by + # the release workflow with the guard's first gate passing at the cut: ratified_head 0849ab8, + # second parent 630475c, descriptor only), ref advanced with the hashes untouched so a firing + # would have been observed rather than assumed: 74 pins resolved against the pinned ref, 0 basis-loss, 0 content-drift, 1 shadowed id(s). + # The prediction held in every limb. Nothing to re-instrument. + ref: v5.15.2 # tag, never a branch # Five pin batches below carried a "[PROPOSED]" marker on their group comment. Each batch's # decision is filed and ratified (DDD-dec-27, -28, -34, -38); the markers were struck # 2026-10-26 (DDD-dec-40). The comments keep their dated reasoning. diff --git a/meta/sessions/2026-10-26-housekeeping/successor-items.md b/meta/sessions/2026-10-26-housekeeping/successor-items.md index 99b090d..00c910e 100644 --- a/meta/sessions/2026-10-26-housekeeping/successor-items.md +++ b/meta/sessions/2026-10-26-housekeeping/successor-items.md @@ -20,6 +20,6 @@ New this session: | # | Item | What it needs | |---|---|---| -| H-1 | **The bump.** `graph/upstream.yaml` is staged at `claude/release-head-guard`. | On Emil's acceptance of upstream PR #26: ref → `v5.15.2`, checker run with hashes untouched, observation recorded in `DDD-dec-40` against `pin-advance-prediction.md`. | +| H-1 | **The bump.** | **Closed.** PR #26 merged (`084bce7`), `v5.15.2` cut under the guard, ref → `v5.15.2` with hashes untouched. Observed: 74 pins resolved against the pinned ref, 0 basis-loss, 0 content-drift, 1 shadowed id(s). Prediction held in every limb; recorded in `DDD-dec-40`. | | H-2 | **The three address review flags.** `DDD-address-01` (two), `DDD-address-03` (one). | Ruled together when S-3 and S-4 land. | | H-3 | **The org-03 / org-04 two-limb warnings.** The validator flags both statements as joining two limbs. | Adjudicate (split or keep) at the next canon session that touches the org set; not a housekeeping edit, since a split mints an id. |