From 44b0bec43eba99ee50f777e1df19450550ca9313 Mon Sep 17 00:00:00 2001 From: DavidHLP Date: Sat, 10 Oct 2026 20:38:08 -0700 Subject: [PATCH 1/2] docs(agent): document V10 through V12 acceptance rollover --- docs/DEVELOPMENT.md | 22 +++++++++++++++++++ .../data/repository_corpus_manifest.json | 4 ++-- 2 files changed, 24 insertions(+), 2 deletions(-) diff --git a/docs/DEVELOPMENT.md b/docs/DEVELOPMENT.md index 01779953c..dfe00ff24 100644 --- a/docs/DEVELOPMENT.md +++ b/docs/DEVELOPMENT.md @@ -483,6 +483,28 @@ and complete receipts before the earlier chain. All failed-run commitments and u liabilities remain retained; the replacement requires a fresh complete prefix on the repaired candidate, rather than resuming or relabeling the incomplete development run. +The same explicitly authorized rollover contract applies to the later supported policies: + +| Selected policy | Required permanently halted predecessor | +| --- | --- | +| `acceptance-revalidation-v10` | V9 | +| `acceptance-revalidation-v11` | V10 | +| `acceptance-revalidation-v12` | V11 | + +Before preparation, retain the predecessor ledger, binding and guard at their pinned +fingerprints and preserve the entire earlier history chain. The selected policy's +`revalidation_history.validate_history` path verifies those sources, settled receipts, +known charges, conservative commitments and full unknown liabilities; none becomes a +fresh acceptance receipt or zero-cost settlement. Use `authorized_budget_period.prepare_period` +with the explicitly selected `policy_id`, then `ModelBudget.bind_prepared` with the same +bound identity and private `history_sources`. Do not repair missing history with an empty +ledger or infer authorization from a supported policy name. Pass that identity to the +entry points using `--policy-id` and `ULTICODE_ACCEPTANCE_IDENTITY` as described above. +Each replacement still needs a fresh complete acceptance prefix, including both full +development passes, within its cumulative and per-purpose limits. Earlier periods remain +halted. A halted replacement is not resumed or reset; this runbook grants no automatic +replacement, retries or paid calls. + Issue the evidence-bound U02 gate only after those inputs validate. Gate artifact references are relative to the private directory containing the gate; place the referenced artifacts there: diff --git a/services/agent/data/repository_corpus_manifest.json b/services/agent/data/repository_corpus_manifest.json index 3a851e41b..5e0590b7a 100644 --- a/services/agent/data/repository_corpus_manifest.json +++ b/services/agent/data/repository_corpus_manifest.json @@ -29,8 +29,8 @@ }, { "doc_id": "repository-development", - "version": "sha256-1c13c0c03785e220057a4febdbfb369a0669e9459884d245b65a2a3288ac6466", - "chunk_id": "repository-development:sha256-1c13c0c03785e220057a4febdbfb369a0669e9459884d245b65a2a3288ac6466:1", + "version": "sha256-e45cc8f3a552b39cb09b2afc14901df254e1ca8d2dd4306cc44df109d128c0e0", + "chunk_id": "repository-development:sha256-e45cc8f3a552b39cb09b2afc14901df254e1ca8d2dd4306cc44df109d128c0e0:1", "source_path": "docs/DEVELOPMENT.md", "access_scope": "repository-public", "sample_kind": "real", From 05d9c436791c723db130d3dc9b0dccc4288ca02d Mon Sep 17 00:00:00 2001 From: DavidHLP Date: Sat, 10 Oct 2026 20:39:57 -0700 Subject: [PATCH 2/2] docs(agent): include explicit bound activation before acceptance --- docs/DEVELOPMENT.md | 3 +++ services/agent/data/repository_corpus_manifest.json | 4 ++-- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/DEVELOPMENT.md b/docs/DEVELOPMENT.md index dfe00ff24..0d799fa98 100644 --- a/docs/DEVELOPMENT.md +++ b/docs/DEVELOPMENT.md @@ -499,6 +499,9 @@ fresh acceptance receipt or zero-cost settlement. Use `authorized_budget_period. with the explicitly selected `policy_id`, then `ModelBudget.bind_prepared` with the same bound identity and private `history_sources`. Do not repair missing history with an empty ledger or infer authorization from a supported policy name. Pass that identity to the +entry points only after the returned bound coordinator's explicit `activate()` step, +under the same approved authorization and history checks. Preparation and binding +alone do not enable billing; activation never reopens a halted predecessor. Select the entry points using `--policy-id` and `ULTICODE_ACCEPTANCE_IDENTITY` as described above. Each replacement still needs a fresh complete acceptance prefix, including both full development passes, within its cumulative and per-purpose limits. Earlier periods remain diff --git a/services/agent/data/repository_corpus_manifest.json b/services/agent/data/repository_corpus_manifest.json index 5e0590b7a..b9925d560 100644 --- a/services/agent/data/repository_corpus_manifest.json +++ b/services/agent/data/repository_corpus_manifest.json @@ -29,8 +29,8 @@ }, { "doc_id": "repository-development", - "version": "sha256-e45cc8f3a552b39cb09b2afc14901df254e1ca8d2dd4306cc44df109d128c0e0", - "chunk_id": "repository-development:sha256-e45cc8f3a552b39cb09b2afc14901df254e1ca8d2dd4306cc44df109d128c0e0:1", + "version": "sha256-1212087248a62b8e5e242dbff8680051d208b416eca84fb543d7f3ba2c0ccdfc", + "chunk_id": "repository-development:sha256-1212087248a62b8e5e242dbff8680051d208b416eca84fb543d7f3ba2c0ccdfc:1", "source_path": "docs/DEVELOPMENT.md", "access_scope": "repository-public", "sample_kind": "real",