Skip to content

docs(agent): document V10 through V12 acceptance rollover #266

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
DavidHLP merged 2 commits into from
Oct 11, 2026
Merged

docs(agent): document V10 through V12 acceptance rollover #266

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
44b0bec
docs(agent): document V10 through V12 acceptance rollover
DavidHLP Oct 11, 2026
05d9c43
docs(agent): include explicit bound activation before acceptance
DavidHLP Oct 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions docs/DEVELOPMENT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -483,6 +483,31 @@ 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 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
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:

Expand Down
4 changes: 2 additions & 2 deletions services/agent/data/repository_corpus_manifest.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,8 +29,8 @@
},
{
"doc_id": "repository-development",
"version": "sha256-1c13c0c03785e220057a4febdbfb369a0669e9459884d245b65a2a3288ac6466",
"chunk_id": "repository-development:sha256-1c13c0c03785e220057a4febdbfb369a0669e9459884d245b65a2a3288ac6466:1",
"version": "sha256-1212087248a62b8e5e242dbff8680051d208b416eca84fb543d7f3ba2c0ccdfc",
"chunk_id": "repository-development:sha256-1212087248a62b8e5e242dbff8680051d208b416eca84fb543d7f3ba2c0ccdfc:1",
"source_path": "docs/DEVELOPMENT.md",
"access_scope": "repository-public",
"sample_kind": "real",
Expand Down