Skip to content
Merged
7 changes: 7 additions & 0 deletions core/claims/DDD-address-03.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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.
2 changes: 1 addition & 1 deletion core/claims/DDD-org-01.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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.
2 changes: 1 addition & 1 deletion core/claims/DDD-org-02.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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.
2 changes: 1 addition & 1 deletion core/claims/DDD-org-03.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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/.
2 changes: 1 addition & 1 deletion core/claims/DDD-org-04.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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.
2 changes: 1 addition & 1 deletion core/claims/DDD-sim-01.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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.
2 changes: 1 addition & 1 deletion core/claims/DDD-sim-02.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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.
4 changes: 3 additions & 1 deletion core/claims/DDD-track-01.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
6 changes: 4 additions & 2 deletions core/decisions/DDD-dec-27.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
6 changes: 4 additions & 2 deletions core/decisions/DDD-dec-28.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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.
Expand Down
95 changes: 95 additions & 0 deletions core/decisions/DDD-dec-40.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,95 @@
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.

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.
31 changes: 24 additions & 7 deletions graph/upstream.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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,
Expand Down Expand Up @@ -116,7 +119,21 @@ 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. 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.
pins:
# basis claims for DDD-dec-04 (the split decision itself rests on these)
- id: DDD-frame-01
Expand Down Expand Up @@ -241,7 +258,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
Expand Down Expand Up @@ -293,7 +310,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
Expand Down Expand Up @@ -344,15 +361,15 @@ 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
content_hash: sha256:7714da9eb209a6839b862a36c0aecd48d411f6af18cab4b1acaa7a1dea032167
- 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
Expand All @@ -373,7 +390,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.
Expand Down
Loading
Loading