From 0aa55e25467a0ee44684ff686adcec3a26e161d5 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 2 Sep 2026 06:45:52 +0000 Subject: [PATCH 1/4] G3 (draft-pending-ruling): the registry wave and W1's upstream body MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Three registry entries move, all unpinned: term:overflow completes its own parallel (exceeds hold capacity); term:poisoned-ground gains its one state-naming sentence; term:verdict's S5 phrase moves. Three embeds re-project. None of the seven pinned entries moves — the definitional layer is already correct under the ratified precedents. W1 upstream: ground distribution -> deployment distribution across core/09, four measure claims, core/06, core/13, README, live meta; asset docstrings and comments only, outputs verified byte-identical; every filename keeps its name. Exactly two pin digests move, both predicted by id and hash before the edit: DDD-measure-01, DDD-measure-16. Validators at baseline: 0 errors, 66 warnings identical by content; 63 claims, 32 warnings; 12 decisions. Basis: SR-5; SR-6; term:delivery; DDD-measure-12; P-02, P-04, P-05, P-07, P-13, P-16 (downstream gate2-precedents.md); DDD-dec-29 pattern Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_013hHzvy1FUXQXk2KpYHbeJg --- README.md | 2 +- core/00-primitives.md | 3 ++- core/06-composition.md | 2 +- core/09-the-measure.md | 20 ++++++++++---------- core/11-the-floor-mechanism.md | 4 ++-- core/13-delivery.md | 2 +- core/assets/measure-aggregate-discharge.py | 4 ++-- core/assets/measure-mdl-demo.py | 2 +- core/assets/measure-nonuniform-ground.py | 10 +++++----- core/claims/DDD-measure-01.yaml | 2 +- core/claims/DDD-measure-11.yaml | 2 +- core/claims/DDD-measure-12.yaml | 6 +++--- core/claims/DDD-measure-16.yaml | 4 ++-- core/graph/terms.yaml | 7 ++++--- meta/lineage-and-limits.md | 2 +- meta/measure-paper-context.md | 4 ++-- meta/repo-topology.md | 2 +- 17 files changed, 40 insertions(+), 38 deletions(-) diff --git a/README.md b/README.md index 50ee0cd..db068d8 100644 --- a/README.md +++ b/README.md @@ -238,7 +238,7 @@ See [`core/06-composition.md`](core/06-composition.md). For the region in which the acceptance predicate closes, the informal conservation principle admits an exact information-theoretic construction. -Let `V` be the verdict induced by the task over the ground distribution. +Let `V` be the verdict induced by the task over the deployment distribution. Then determination demand is identified as: diff --git a/core/00-primitives.md b/core/00-primitives.md index c9fe097..389bb41 100644 --- a/core/00-primitives.md +++ b/core/00-primitives.md @@ -95,7 +95,8 @@ The apparatus holds against this without strain: > **Poisoned ground** — ground that is present but false: the substrate a determination reads has > been corrupted, so a correct determiner resolves wrongly with full authority. The logic is -> sound; the ground is the attack surface. +> sound; the ground is the attack surface. The state it names: **ground that reached the act +> false** — what arrived is wrong, not missing. diff --git a/core/06-composition.md b/core/06-composition.md index c04fec8..d951e94 100644 --- a/core/06-composition.md +++ b/core/06-composition.md @@ -172,7 +172,7 @@ judgment into encoding, and an **inheritance path** from encoding to the next ru A composed arrangement executing one act is the two primitives twice over. From outside the declared boundary, the composite is **one actor**: one capability envelope (`04`), one verdict owed. Inside the boundary, the wiring — who reads what, which member resolves which slice, what -sits at the seam — is declared structure, exactly as the decomposition and the ground +sits at the seam — is declared structure, exactly as the decomposition and the deployment distribution are. Nothing about being composed requires anything beyond the act. Synchronic does not mean timeless. Sequence exists within the episode — members fire in order, diff --git a/core/09-the-measure.md b/core/09-the-measure.md index 781e443..ed90b3b 100644 --- a/core/09-the-measure.md +++ b/core/09-the-measure.md @@ -28,7 +28,7 @@ exposition (canon authority lives in the claim files; see `core/claims/README.md | §7 | The construction is available to an arrangement exactly where its predicate closes; existence and estimability are separate conditions | `DDD-measure-16` | | §7 | The construction's domain and the non-zero-floor region coincide — principled, not evidential | `DDD-measure-17` | | §7, §9 | The measure prices the verdict, not the search | `DDD-measure-11` | -| §9 | Demand is relative to the ground distribution | `DDD-measure-12` | +| §9 | Demand is relative to the deployment distribution | `DDD-measure-12` | | §2.1 | Admissibility: the engineering reading holds for admissible `X` only | `DDD-measure-15` | | §9 | The chain rule iterates; the conditional term is an internal seam | `DDD-measure-14` | | §7a | Outcome and verdict: the determinate's two registers | `DDD-frame-14` | @@ -63,7 +63,7 @@ So demand is not a count. It is a **measure**. And the measure is **Shannon info > arrangement (`term:closure`; *decidable* is the formal special case, not the requirement), > the predicate evaluates outcomes, and the **task class** supplies one correct output per > input point. The **verdict** is that induced assignment — the correct output over each point -> of the input space. Let `P` be the distribution over inputs (the *ground distribution*). The +> of the input space. Let `P` be the distribution over inputs (the *deployment distribution*). The > **determination demand** of the task is the Shannon entropy of the verdict: > > **D = H(verdict)**, measured in **bits**. @@ -266,7 +266,7 @@ form of the unification of conservation with the actor model — and it corrects > mere relabelled difficulty). Demand is "constant *across* actors, *allocated by* actor."** The same > `H(verdict)` faces every actor; the actor sets only how it splits between encoded and judgment. -`H(verdict)` never mentions the actor. It is a property of the verdict function and the ground +`H(verdict)` never mentions the actor. It is a property of the verdict function and the deployment distribution — the task. That is exactly why it is "fixed by the task, never by the system." ### 6.3 X = what is supplied before the act → the encode/verify split @@ -459,7 +459,7 @@ concession. A distribution-free quantity cannot express it. Second, the objects differ. MDL is computable — that is its purpose — but it prices the description of a hypothesis against data. It is model-selection machinery. Verdict entropy prices the distinctions a task requires of whatever resolves it. The two reconcile rather than compete: by the source-coding -theorem, `H(V)` is the expected length of an optimal description of the verdict under the ground +theorem, `H(V)` is the expected length of an optimal description of the verdict under the deployment distribution. The measure proposed here is therefore itself a description-length quantity — the distribution-relative expectation, which is the form a deployed system faces. @@ -498,7 +498,7 @@ from it (`core/11` §4), and that bound supplies the escape/judgment split that supply is partial: the mechanism is sufficient for escape and not necessary for it (`core/11` §7). **Brooks (1987).** "No Silver Bullet" claims an essential complexity fixed by the problem. `H(V)` gives -that claim an exact form and a boundary: fixed by the task, the tolerance, and the ground distribution +that claim an exact form and a boundary: fixed by the task, the tolerance, and the deployment distribution — and never by the actor — where the predicate closes, and only there. ### References @@ -533,21 +533,21 @@ Three, none fatal, all required in any write-up: decomposition with conditioning. That identification is falsifiable and was vindicated on the example — but it must be claimed as a modelling result, never as a mathematical discovery. -2. **Demand is relative to the ground distribution.** `H(verdict)` depends on `P(input)`; the +2. **Demand is relative to the deployment distribution.** `H(verdict)` depends on `P(input)`; the example used uniform. So *"fixed by the task"* must be stated as *"fixed by the task, the - tolerance, and the ground distribution."* This is arguably more correct — the same validator + tolerance, and the deployment distribution."* This is arguably more correct — the same validator faces different demand in different deployment environments — but it is an added parameter, not a free lunch. 3. **Five instances is credibility, not certification.** The identity is general (it is the chain rule), and it has now been exercised on five conditioning variables — decomposition, actor encoding, what is supplied before the act (empirically, with distractors), a decomposition - applied *twice*, and a decomposition under varied ground — all on closing-predicate tasks. That + applied *twice*, and a decomposition under varied deployment distributions — all on closing-predicate tasks. That is real triangulation, not a single toy. Two of the three cases this caveat previously named as owed are now worked: **chained seams** (`core/assets/measure-chained-seams.py`, claim `DDD-measure-14` — both chain orders re-split the seam and leave the parts residual invariant) - and **non-uniform ground** (`core/assets/measure-nonuniform-ground.py`, claim `DDD-measure-12` — - the identity holds exactly under three ground distributions while the demand itself moves by a + and **non-uniform deployment distribution** (`core/assets/measure-nonuniform-ground.py`, claim `DDD-measure-12` — + the identity holds exactly under three deployment distributions while the demand itself moves by a factor of six). **Multi-actor compositions remain owed**, and the debt is not reduced by the chained-seam instance: there the conditioning variables are sub-decompositions of one task, and the composition case conditions on *actor encodings*. Same arithmetic, distinct instance, diff --git a/core/11-the-floor-mechanism.md b/core/11-the-floor-mechanism.md index 4f5009d..411ca76 100644 --- a/core/11-the-floor-mechanism.md +++ b/core/11-the-floor-mechanism.md @@ -50,12 +50,12 @@ Effective capacity is `min(C_hold, C_resolve)`, but the two produce different es -> **Hold-overflow** — the decision's governing ground does not fit. **Resolve-overflow** — +> **Hold-overflow** — the decision's governing ground exceeds hold capacity. **Resolve-overflow** — > the ground fits and is held, but the bits that must be *jointly resolved* exceed resolve > capacity. -- **Hold-overflow** — the decision's governing ground does not fit; the actor decides against a +- **Hold-overflow** — the decision's governing ground exceeds hold capacity; the actor decides against a *partial view*. This is **encodable away**: pre-resolve some ground into the constraint (raise `I(verdict;X)`) and the residual that must be held shrinks until it fits. RAG is this move. Not floor. diff --git a/core/13-delivery.md b/core/13-delivery.md index 958d70b..77b3f3c 100644 --- a/core/13-delivery.md +++ b/core/13-delivery.md @@ -138,7 +138,7 @@ supply is produced per act; there is no act-free discharge. Governance never cho demand is supplied — only *by what*, chosen in advance or defaulted at the act. **Distribution-weighting — an exposition note, deliberately not a claim.** Discharge is -distribution-weighted: demand comes due where acts concentrate, at the rate the ground +distribution-weighted: demand comes due where acts concentrate, at the rate the deployment distribution `P` supplies them. This is the measure's own `P` (`core/09`) read back, a projection of the measure rather than a further claim, and it files as this paragraph — the flag is the finding. diff --git a/core/assets/measure-aggregate-discharge.py b/core/assets/measure-aggregate-discharge.py index 315402b..1d39ecc 100644 --- a/core/assets/measure-aggregate-discharge.py +++ b/core/assets/measure-aggregate-discharge.py @@ -21,7 +21,7 @@ The i.i.d. control redraws the month at every act. It must return exactly N*H(V) — the equality limb of the inequality, demonstrated rather than stated. -Task, denomination (bits x n) and ground distribution as in measure-toy.py; +Task, denomination (bits x n) and deployment distribution as in measure-toy.py; entropies are exact (exhaustive, log-space), nothing is sampled. Exercises DDD-frame-16 (discharge is act-indexed) as worked arithmetic. @@ -31,7 +31,7 @@ LOG2E = 1.0 / log(2.0) -# Task: validate (M, D). VALID iff D <= days_in_month(M). Uniform ground. +# Task: validate (M, D). VALID iff D <= days_in_month(M). Uniform deployment distribution. days = {1: 31, 2: 28, 3: 31, 4: 30} points = [(m, d) for m in days for d in range(1, 32)] verdict = {(m, d): (d <= days[m]) for (m, d) in points} diff --git a/core/assets/measure-mdl-demo.py b/core/assets/measure-mdl-demo.py index 6a8f48b..7e26f35 100755 --- a/core/assets/measure-mdl-demo.py +++ b/core/assets/measure-mdl-demo.py @@ -25,7 +25,7 @@ projected rate-split (DDD-cost-03). Coefficients stipulated, not measured. Task (identical to measure-toy.py figures): (M, D), M in 1..4, D in 1..31, -uniform ground, verdict VALID iff D <= days(M), days = {31, 28, 31, 30}. +uniform deployment distribution, verdict VALID iff D <= days(M), days = {31, 28, 31, 30}. """ import itertools diff --git a/core/assets/measure-nonuniform-ground.py b/core/assets/measure-nonuniform-ground.py index 4935d78..5042e4e 100644 --- a/core/assets/measure-nonuniform-ground.py +++ b/core/assets/measure-nonuniform-ground.py @@ -1,12 +1,12 @@ """ -Non-uniform ground for "Specification Demand Is Verdict Entropy." +Non-uniform deployment distribution for "Specification Demand Is Verdict Entropy." Re-runs the date task under skewed input distributions and verifies the identity H(V) = I(V;S) + H(V|S) per deployment: same task, same code, same decompositions — demand moved by the -ground distribution alone. Exercises DDD-measure-12 (demand is relative to the -ground distribution) as a worked instance rather than a stated caveat. +deployment distribution alone. Exercises DDD-measure-12 (demand is relative to the +deployment distribution) as a worked instance rather than a stated caveat. Task and denomination (bits x n) as in measure-toy.py; entropies are exact (weighted, exhaustive), nothing is sampled. @@ -29,7 +29,7 @@ def H(pairs): return -(p * log2(p) + (1 - p) * log2(1 - p)) def analyze(split, weight): - """(parts, seam, whole) in bits x n under the weighted ground distribution.""" + """(parts, seam, whole) in bits x n under the weighted deployment distribution.""" all_pairs = [(weight(p), verdict[p]) for p in points] tot = sum(w for w, _ in all_pairs) Hv = H(all_pairs) @@ -42,7 +42,7 @@ def analyze(split, weight): Hc += (sum(w for w, _ in pairs) / tot) * H(pairs) return n * Hc, n * (Hv - Hc), n * Hv -# Deployments: the ground distribution the task faces, nothing else varied. +# Deployments: the deployment distribution the task faces, nothing else varied. deployments = [ ("benign (valid 9x invalid)", lambda p: 9.0 if verdict[p] else 1.0), ("uniform (the worked example)", lambda p: 1.0), diff --git a/core/claims/DDD-measure-01.yaml b/core/claims/DDD-measure-01.yaml index ddab861..756a457 100644 --- a/core/claims/DDD-measure-01.yaml +++ b/core/claims/DDD-measure-01.yaml @@ -2,7 +2,7 @@ format: 1 id: DDD-measure-01 kind: empirical statement: | - Specification demand is verdict entropy: for a task whose acceptance predicate closes, the demand engineers experience as specification burden is H(V) over the ground distribution. + Specification demand is verdict entropy: for a task whose acceptance predicate closes, the demand engineers experience as specification burden is H(V) over the deployment distribution. status: projected region: closing predicates only evidence: diff --git a/core/claims/DDD-measure-11.yaml b/core/claims/DDD-measure-11.yaml index 586afe6..03fb7f3 100644 --- a/core/claims/DDD-measure-11.yaml +++ b/core/claims/DDD-measure-11.yaml @@ -3,7 +3,7 @@ id: DDD-measure-11 kind: conceptual statement: > The measure prices the verdict, not the search: H(verdict) is a property of the verdict - function and the ground distribution and says nothing about the cost of computing a + function and the deployment distribution and says nothing about the cost of computing a correct answer. Two tasks with identical verdict entropy can differ unboundedly in generation cost, so the measure must not be read as pricing generation. status: reported diff --git a/core/claims/DDD-measure-12.yaml b/core/claims/DDD-measure-12.yaml index 6e7cd5f..5986582 100644 --- a/core/claims/DDD-measure-12.yaml +++ b/core/claims/DDD-measure-12.yaml @@ -2,8 +2,8 @@ format: 1 id: DDD-measure-12 kind: conceptual statement: > - Demand is relative to the ground distribution: H(verdict) depends on P(input), so "fixed - by the task" must be read as "fixed by the task, the tolerance, and the ground + Demand is relative to the deployment distribution: H(verdict) depends on P(input), so "fixed + by the task" must be read as "fixed by the task, the tolerance, and the deployment distribution" — the same validator faces different demand in different deployment environments. status: reported @@ -15,7 +15,7 @@ evidence: - kind: asset ref: core/assets/measure-nonuniform-ground.py note: >- - the date task under three ground distributions — uniform, adversarial (invalid 9x valid), and + the date task under three deployment distributions — uniform, adversarial (invalid 9x valid), and benign. Whole demand moves from 25.493 to 96.639 to a sixth of uniform while the identity holds exactly in every deployment, and a fixed decomposition's seam share moves with the distribution (41% benign, 57% uniform, 75% adversarial). Re-run 2026-08-17 after promotion diff --git a/core/claims/DDD-measure-16.yaml b/core/claims/DDD-measure-16.yaml index 78c64f3..7e55c91 100644 --- a/core/claims/DDD-measure-16.yaml +++ b/core/claims/DDD-measure-16.yaml @@ -2,7 +2,7 @@ format: 1 id: DDD-measure-16 kind: formal statement: | - The verdict-entropy construction is available to an arrangement exactly where the task's acceptance predicate closes for that arrangement; availability is a property of the arrangement, not of the task, and it is neither the existence of the verdict function nor the estimability of the ground distribution. + The verdict-entropy construction is available to an arrangement exactly where the task's acceptance predicate closes for that arrangement; availability is a property of the arrangement, not of the task, and it is neither the existence of the verdict function nor the estimability of the deployment distribution. status: established region: | Arrangements, not tasks: closure is closure for an arrangement (term:closure), so availability @@ -21,7 +21,7 @@ region: | exists until the task supplies a tie-breaker, a canonical form, or a declared selection distribution. - ESTIMABILITY. H(V) is taken with respect to P, the ground distribution (core/09 §2), so P must + ESTIMABILITY. H(V) is taken with respect to P, the deployment distribution (core/09 §2), so P must be known well enough to estimate. Where the deployment distribution is unknown, unstable, non-stationary, or only partly observable, the demand is well defined and cannot be computed (DDD-measure-12). A verdict function alone does not deliver a number. diff --git a/core/graph/terms.yaml b/core/graph/terms.yaml index ee03fc1..633ae6e 100644 --- a/core/graph/terms.yaml +++ b/core/graph/terms.yaml @@ -86,7 +86,8 @@ terms: canonical_md: | > **Poisoned ground** — ground that is present but false: the substrate a determination reads has > been corrupted, so a correct determiner resolves wrongly with full authority. The logic is - > sound; the ground is the attack surface. + > sound; the ground is the attack surface. The state it names: **ground that reached the act + > false** — what arrived is wrong, not missing. - id: term:granularity-bound term: granularity-bound aliases: [granularity bound] @@ -384,7 +385,7 @@ terms: > arrangement (`term:closure`; *decidable* is the formal special case, not the requirement), > the predicate evaluates outcomes, and the **task class** supplies one correct output per > input point. The **verdict** is that induced assignment — the correct output over each point - > of the input space. Let `P` be the distribution over inputs (the *ground distribution*). The + > of the input space. Let `P` be the distribution over inputs (the *deployment distribution*). The > **determination demand** of the task is the Shannon entropy of the verdict: > > **D = H(verdict)**, measured in **bits**. @@ -441,7 +442,7 @@ terms: established_by: 11-the-floor-mechanism.md status: settled canonical_md: | - > **Hold-overflow** — the decision's governing ground does not fit. **Resolve-overflow** — + > **Hold-overflow** — the decision's governing ground exceeds hold capacity. **Resolve-overflow** — > the ground fits and is held, but the bits that must be *jointly resolved* exceed resolve > capacity. - id: term:escape-mechanism diff --git a/meta/lineage-and-limits.md b/meta/lineage-and-limits.md index 7c38be6..41c99ca 100644 --- a/meta/lineage-and-limits.md +++ b/meta/lineage-and-limits.md @@ -387,7 +387,7 @@ rather than be caught by: - **Minimum description length / Kolmogorov complexity** (Solomonoff, Kolmogorov, Rissanen) — an alternative formalisation of "how much specification does this task require." `core/09` uses - Shannon entropy over a ground distribution instead, which is *weaker but computable*. Worth a + Shannon entropy over a deployment distribution instead, which is *weaker but computable*. Worth a sentence in any paper explaining the choice: MDL would give a distribution-free measure but is uncomputable; entropy is distribution-relative but calculable, which is what let us actually compute the worked examples. diff --git a/meta/measure-paper-context.md b/meta/measure-paper-context.md index 75e3efc..3ed51e4 100644 --- a/meta/measure-paper-context.md +++ b/meta/measure-paper-context.md @@ -40,7 +40,7 @@ the prose is the bug — flag it in the claim's `notes:`, never harmonise silent | Debt | Where booked | State | |---|---|---| -| Chained seams, multi-actor compositions, non-uniform ground | `core/09` §9 caveat 3; `core/06` line 185 | Open, unmoved. The honest filler for the length gap, if one is ever wanted | +| Chained seams, multi-actor compositions, non-uniform deployment distribution | `core/09` §9 caveat 3; `core/06` line 185 | Open, unmoved. The honest filler for the length gap, if one is ever wanted | | Outside certification by an information theorist | `core/09` §9 caveat 3; `core/11` §7 | Open, and now owed twice — `core/11` inherited it | Two further items read as debts and are not. The RAG instance is **not** claimed as evidence of @@ -114,7 +114,7 @@ Thirteen IDs, one retired. Status vocabulary: `established` (formal, follows fro | `DDD-measure-09` | conceptual | reported | paper-1 | Demand is a measure, not a count | | `DDD-measure-10` | formal | established | paper-1 | You cannot decompose your way out | | `DDD-measure-11` | conceptual | reported | paper-1 | The measure prices the verdict, not the search | -| `DDD-measure-12` | conceptual | reported | paper-1 | Demand is relative to the ground distribution | +| `DDD-measure-12` | conceptual | reported | paper-1 | Demand is relative to the deployment distribution | | `DDD-measure-13` | formal | reported | paper-1 | The maturation asymptote is `H(V) − I(V;S_encoded)` | `owner:` names *which projection pays the claim's debt*, per `spec/claim-format.md`. Ten of these are diff --git a/meta/repo-topology.md b/meta/repo-topology.md index 29766a1..fa7abd7 100644 --- a/meta/repo-topology.md +++ b/meta/repo-topology.md @@ -27,7 +27,7 @@ to pin it independently. That is an N*-type decision — the crossover machinery layer applied to repository structure. **Do not split ahead of the crossover.** The seam itself splits across the charter boundary: its arithmetic — the chain-rule identity, -the declared ground distribution — is synchronic and lives with the principle (`core/09`); its +the declared deployment distribution — is synchronic and lives with the principle (`core/09`); its life — choosing `S`, the interface contract, the `I(V;S)` ↔ interface-cost correspondence with its `closesAt`, amortisation over `N` — persists between acts and lives with the ledger layer (`decision-driven-design`). From 44dee42e6cf1a303548854e97f513883f33a7ce9 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 2 Sep 2026 07:07:09 +0000 Subject: [PATCH 2/4] G4 (draft-pending-ruling): W2's two prose edits under the precedents MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit DDD-frame-17's falsifier aligned to its own statement's act-indexed form (unhashed field — digest verified unmoved); core/13's exhaustiveness sentence aligned the same way. Both cite P-01. The region's identical phrase is HELD: it declares itself carried verbatim from DDD-frame-15, and editing it is a predicted firing Emil has not ruled. Basis: P-01 (downstream gate2-precedents.md); DDD-frame-17; DDD-dec-29 pattern Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_013hHzvy1FUXQXk2KpYHbeJg --- core/13-delivery.md | 2 +- core/claims/DDD-frame-17.yaml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/core/13-delivery.md b/core/13-delivery.md index 77b3f3c..0499783 100644 --- a/core/13-delivery.md +++ b/core/13-delivery.md @@ -90,7 +90,7 @@ timeout has a *when-to-stop* alternative, predetermined by the deadline, and a * alternative, drawn from whatever partial state obtained. **Exhaustiveness here is provable, not enumerated.** Given the standing configuration and the -ground, the resolution is determined or it is not; if it is not, what determines it is inside the +ground at the act, the resolution is determined or it is not; if it is not, what determines it is inside the arrangement's control or outside it. Two dichotomies, three values, no remainder — and a dichotomy, unlike a list, cannot be counterexampled. The claim's content sits in the answerability of that first test, which is where its falsifier now points. diff --git a/core/claims/DDD-frame-17.yaml b/core/claims/DDD-frame-17.yaml index 7c768e7..5b53b00 100644 --- a/core/claims/DDD-frame-17.yaml +++ b/core/claims/DDD-frame-17.yaml @@ -57,7 +57,7 @@ evidence: ref: core/13-delivery.md §4 note: derivation by dichotomy; premises by ID and steps in notes falsifier: | - An outcome-relevant alternative at a completed act for which there is no fact of the matter whether the standing configuration and the ground together determine the resolution; or a completed act with an outcome-relevant alternative resolved by nothing at all. + An outcome-relevant alternative at a completed act for which there is no fact of the matter whether the standing configuration and the ground at the act together determine the resolution; or a completed act with an outcome-relevant alternative resolved by nothing at all. test: | Coding reliability over recorded acts: independent coders assigning every completed act's outcome-relevant alternatives to predetermined, exercised, or drawn without remainder, without collapsing the discharge coding into the store coding, and agreeing on where the fixing test is answerable. owner: none From 5e75d23d0573fc7608b0e8243b2460d6142fa9f5 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 2 Sep 2026 10:40:54 +0000 Subject: [PATCH 3/4] G5 (draft-pending-ruling): two Danish glosses repaired under the file's own rule MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The closure gloss imported 'decided over digital ground' — neither clause is canon's, and 'afgores' collapses the decidable distinction term:closure reserves; re-glossed to observable relevant ground and evaluable adequacy within declared bounds. The poisoned-ground gloss defined the term by one generator (self-consumed output) instead of canon's present-but-false; first clause re-glossed, the correct paraphrase kept. English wins where the two disagree, per the file's own stated rule. Basis: term:closure; term:poisoned-ground; SR-2 Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_013hHzvy1FUXQXk2KpYHbeJg --- i18n/ordliste-dansk.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/i18n/ordliste-dansk.md b/i18n/ordliste-dansk.md index 11d1448..3b24186 100644 --- a/i18n/ordliste-dansk.md +++ b/i18n/ordliste-dansk.md @@ -100,7 +100,7 @@ men escape er ofte bare fravær af en beslutning, ikke forsømmelse).* |---|---|---| | **gulvet** | the floor | Den del af vurderingsbehovet, der **ikke** kan flyttes væk fra aktøren. | | **acceptprædikat** | acceptance predicate | Tjekket, der afgør, om en afgørelse er rigtig. | -| **lukker / lukning** | closes / closure | Om acceptprædikatet kan afgøres over digital grund. | +| **lukker / lukning** | closes / closure | Om den relevante grund er observerbar, og tilstrækkelighed kan evalueres inden for de erklærede grænser. *Afgørbar* er forbeholdt det formelle specialtilfælde. | | **stidegenererethed** | path-degeneracy | Uendeligt mange forskellige afgørelser, der alle rammer et tilstrækkeligt resultat. | > **Gulvet ligger i acceptprædikatet, ikke i beslutningen.** Nul, hvor prædikatet lukker (og der gør @@ -141,7 +141,7 @@ men escape er ofte bare fravær af en beslutning, ikke forsømmelse).* | Dansk | Engelsk | Note | |---|---|---| | **indkod/verificér-delingen** | the encode/verify split | Indkod grund, du kontrollerer; verificér grund, du ikke gør. | -| **forgiftet grund** | poisoned ground | Når en aktør forbruger sit eget tidligere output som grund. Fejl bliver *korrekte slutninger over falske præmisser*. | +| **forgiftet grund** | poisoned ground | Grund, der er til stede, men falsk: substratet, en afgørelse læser, er korrumperet. Fejl bliver *korrekte slutninger over falske præmisser*. | | **lukningsprincippet** | the closure principle | En aktørs eget tidligere output er ikke grund. | --- From 1c58dd60f7bd9196b1429968e64b2cafba8f743c Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 2 Sep 2026 10:52:02 +0000 Subject: [PATCH 4/4] GATE 6 (draft-pending-ruling): propose v5.13.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The ground migration executed: the population sense leaves the word, three unpinned registry entries move, four pinned measure statements carry the rename with their two W6 predicted and verified by hash. Zero of the seed's seven predicted firings occurred — recorded, not manufactured. All validators green; 9 release descriptors valid. Basis: DDD-measure-01; DDD-measure-11; DDD-measure-12; DDD-measure-16; DDD-frame-17; DDD-dec-30; DDD-dec-26; DDD-agent-01 Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_013hHzvy1FUXQXk2KpYHbeJg --- releases/v5.13.0.yaml | 75 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 75 insertions(+) create mode 100644 releases/v5.13.0.yaml diff --git a/releases/v5.13.0.yaml b/releases/v5.13.0.yaml new file mode 100644 index 0000000..40b74d4 --- /dev/null +++ b/releases/v5.13.0.yaml @@ -0,0 +1,75 @@ +format: 1 +version: v5.13.0 +# No `commit`: cut wherever this file lands on the default branch, the normal case +# (spec/release-format.md §2 rule 3). +date: 2026-09-02 +basis: + # The four measure claims whose statements move with the population sense. + - DDD-measure-01 + - DDD-measure-11 + - DDD-measure-12 + - DDD-measure-16 + # The claim whose falsifier is aligned to its own statement's act-indexed form, + # and whose region is deliberately left as declared verbatim carriage. + - DDD-frame-17 + # The naming discipline the executed vocabulary obeys — reuse, never minting. + - DDD-dec-30 + # The ruling that gated ground-provenance minting; the provenance adjectives the + # migration leaves in place are that ruling still holding. + - DDD-dec-26 + # Basis as query: the statement examined, ruled untouched, and left un-fired. + - DDD-agent-01 +title: 'The ground migration, executed — smaller than every instrument predicted' +summary: | + **The deferred migration, executed under twenty ratified precedents.** The predecessor planned + the ground migration completely and deferred it whole, because its first twenty re-expressions + would have set precedents the rest inherited unreviewed. This release is the execution: twenty + precedents ruled individually first, then every remaining occurrence citing exactly one of them + — and the finding is that **the migration is smaller than four instruments in a row predicted**. + Each shrink came from a ruling, not a re-count. + + This is a minor and not a patch: settled canonical text moves in three registry entries, four + pinned claim statements move, and the population sense leaves the word. It is not a major + because every format-1 claim remains valid unchanged, no id moves, and no status moves. + + ### The population sense leaves: `deployment distribution` + + `ground` had been carrying five senses. The one sense that was a genuinely distinct object — + S5, the distribution over inputs a deployed task faces — now has its own name everywhere in + canon: `term:verdict`'s definition, `core/09`'s prose, `core/06`, `core/13`, the `README`, and + the statements of `DDD-measure-01`, `-11`, `-12` and `-16`. The papers moved first (the Paper A + revision); canon now agrees with them. Asset filenames keep their names, and three printed + strings inside `measure-nonuniform-ground.py` deliberately keep the old phrase — the output + bytes are recorded evidence, and they are booked with the filename as one item for whoever next + advances that asset. + + ### The definitional layer was already correct + + The plan predicted seven pinned registry entries moving, with seven W6 firings. **Zero of the + seven fire.** Ruled sentence by sentence under the precedents, every pinned entry's text + already names what is done to the ground — `reading`, `declared`, `observable`, `in context at + once`, `channels`, `held at fixed`, `at the act`. The three entries that do move are unpinned: + `term:overflow` completes its own parallel (*"exceeds hold capacity"*), `term:poisoned-ground` + gains one sentence naming its state (*"ground that reached the act false — what arrived is + wrong, not missing"*), and `term:verdict` takes the population rename. Three embeds re-project. + + ### What fires, stated before it happened + + When the downstream pin next advances past this release, **exactly two W6 fire**: + `DDD-measure-01` and `DDD-measure-16`, whose statements carry the population rename. Both were + predicted by id and hash before the edit, and both landed on the predicted hash exactly. Zero + W5, zero W7. `DDD-frame-17`'s digest is verified unmoved: its falsifier (unhashed) is aligned + to the statement's own *"at the act"* form, and its region — which declares itself carried + verbatim from `DDD-frame-15` — is left, a declared carriage inside a hashed field. + + ### The prose, ruled rather than rewritten + + Of the corpus's bare occurrences in canon and the projection, the wave bodies held 131 rows and + the surfaced remainder 54. Every row now cites exactly one precedent in a committed citation + map. **Seven sentences were edited.** The rest were already correct — the vocabulary was doing + its work in canon's habits, and the rulings are what made that checkable. Two Danish glosses + are repaired under the glossary's own English-wins rule; `apparatus/encode-verify.md` stops + attributing its read-only-surface gloss to `core/00` and owns it. + + The classification, the citation maps, the instruments and the per-gate rulings live in the + projection repository's session record (`meta/sessions/2026-08-31-ground-migration-exec/`).