Authorization for Self-Modifying AI Agent Populations: Conserving Authority across Replacement, Forking, and Rollback
Organizations: Accentrust, Vancouver, Canada · Georgia Institute of Technology, Atlanta, Georgia, USA · University of Illinois Urbana-Champaign, Urbana, Illinois, USA
Abstract
Self-modifying AI agents can replace, fork, and roll back identity-bearing software while descendants remain executable. Per-successor authorization does not constrain the resulting population: siblings may duplicate quotas, combine permissions, survive ancestor cuts, or overlap predecessors during promotion. We define authorization succession, which conserves authority across the active frontier of a single-parent generation forest. Our external protocol binds each generation to a manifest, root, unique parent, complete lineage, and fresh population sequence. Separate invariants bound root-lifetime consumption and current population exposure. A staged reservation freezes predecessor residual authority during replacement, while a partitioning fork validates the complete child family. Each commit atomically fences the predecessor and activates successors. Ancestor cuts invalidate dependent descendants; rollback creates a fresh generation without restoring spent authority; and a new root requires an independent grant. Under complete mediation, authenticated records, sound effect abstraction, durable monotone state, and complete lineage accounting, we prove population-safe succession, fork conservation, revocation closure, atomic handoff, rollback non-reminting, and exclusion of self-certification. An executable evaluation covers 32 registered decisions through direct-call and mailbox mappings (64/64 replays; 28 allows, 36 denies). An independent checker accepts all 64 original traces and rejects 28/28 semantic mutants; 12/12 profile invariants, 16/16 crash cuts, and 32/32 contender schedules pass. Two external adapters reproduce all 32 decisions around measured OurArk and Darwin Godel Machine mutations, including fresh-process restart, atomic succession, and predecessor rejection. The results establish authorization succession for registered protected effects.
Figures & tables
| Execution | Locally acceptable observation | Population violation | Required state |
|---|---|---|---|
| Sibling duplication | Both children remain below the parent’s individual ceiling | The pair receives two copies of one budget or executor share | Aggregate allocation and residual |
| Relational splice | Each branch exposes only an allowed field projection | Branch coordination synthesizes a complete effect tuple never certified by one authority witness | Complete effect relation and holder ownership |
| Ancestor-revoke leak | Offline descendant presents a previously valid child authorization record | Its witness still depends on the revoked ancestor atom | Lineage cut and complete frontier |
| Dual-active promotion | New generation activates; predecessor fence is retried after a crash | Old and new generations both reach the protected sink | Atomic replacement commit |
| Rollback replay | Historical body digest and old authorization record match | Retired sequence, spent budget, or revoked grant is reused | Fresh generation sequence and monotone identity/state guards |
| Self-certification | Distinct certifier identifiers approve a candidate | All certifiers are declared under the candidate’s control root | Evidence-root independence |
| ID | Assumption | Enforced obligation |
|---|---|---|
| A1 | Complete effect mediation | Every security-relevant commitment named by the profile crosses a broker that validates the current generation, complete lineage-atom closure, allocation, and complete effect tuple at its own linearization point. |
| A2 | Authentic canonical identity | Generation identities, the unique authorization parent, body/configuration commitments, authorization and certification records, cuts, allocations, receipts, and evidence-root identities use unambiguous canonical encodings and authenticators whose acceptance cannot be produced from the candidate’s control root alone. |
| A3 | Durable monotone generations | Generation and root epochs never decrease or reactivate; accepted evidence/authorization records, lineage cuts, fences, root-lifetime debit records, and effect-request replay records cannot be rewritten. |
| A4 | Complete lineage accounting | Every non-root generation has exactly one registered authorization parent before activation. A fork may create several successors atomically, but each successor names the same single predecessor; the predecessor is fenced. The ledger retains every resulting parent edge and lineage atom across offline, delayed, and nested descendants until a terminal cut or independent re-root removes authority. |
| A5 | Sound population algebra | Effect normalization preserves every policy-relevant correlation; the registered effect-membership predicate and authority join are monotone, multiplicity-aware where policy requires it, additive for consumable resources, and conservative for unknown fields. |
| A6 | Atomic population transactions | Reservation, allocation replacement, activation, predecessor fencing, and budget consumption execute as serializable durable transitions with exact population-version and source-residual preconditions. A held reservation either blocks predecessor consumption or is made stale by it. |
| Layer | Bound fact | Security role |
|---|---|---|
| Reference manifest | code digest, control path, enforcement-configuration digest, memory-policy digest, model-route digest, policy-compiler digest, proposer identifier, Skill-closure digest | fixes the exact eight-field executable schema |
| Reference lineage | population and root identifiers, root epoch and grant digest, one parent-generation identifier, complete lineage-atom set | makes single-parent succession and fork ancestry explicit |
| Reference lifetime | fresh population-issued generation sequence | separates launches and blocks historical identity replay |
| Reference evidence | proposer and certifier principals mapped through frozen control roots; subject-manifest and evidence digests | checks digest binding and declared-root separation |
| Registered extension | any additional prompt, tool, harness, dependency, normalizer, or profile field named by a larger governed schema | extends the abstract identity obligation only when a deployment resolves and binds it |
| Contract field | Direct-call source | Message-mailbox source |
|---|---|---|
| Authorization parent | typed predecessor identifier | topic-handler predecessor identifier |
| Body commitment | canonical manifest fields | canonical manifest fields |
| Generation freshness | ledger-owned sequence assigned during the command | ledger-owned sequence assigned while handling the message |
| Evidence | direct certification command | certification topic and handler |
| Requested authority | direct reservation command | reservation topic and handler |
| Lifecycle signal | explicit succession operation | versioned succession message |
| Group | Cases | Expected | Distinguishing obligation |
|---|---|---|---|
| Mutation surfaces | code, model route, Skill/dependency closure, memory policy, policy compiler, enforcement configuration safe refactor | 6 Allow | exact effect relation and control path preserved |
| Mutation surfaces | same six surfaces safe narrowing | 6 Allow | strict sub-allocation with no returned spent resource |
| Mutation surfaces | same six surfaces effect expansion | 6 Deny | requested tuple/share exceeds parent or population residual |
| Mutation surfaces | same six surfaces control-path weakening | 6 Deny | identity, evidence, ledger, or broker mediation removed |
| Legal succession | single replacement; independent re-root | 2 Allow | atomic old/new handoff; old-lineage dependence explicitly severed |
| Population attacks | sibling split; nested-successor laundering | 2 Deny | aggregate allocation cannot be copied or hidden by depth |
| Evidence family | Frozen denominator | Result and interpretation |
|---|---|---|
| Logical corpus | 32 cases; 14 Allow , 18 Deny | 32/32 matched the registered verdict under the reference mechanism |
| Command-surface mappings | 32 direct-call + 32 mailbox replays | 64/64 matched; 28 allows, 36 denies; zero cross-mapping disagreement |
| Independent checking | 64 complete traces | 64/64 accepted after independent reconstruction |
| Semantic regressions | 28 outer-resealed mutants | 28/28 rejected for the registered semantic or denominator violation |
| Reference-profile invariants | 12 targeted probes | 12/12 passed: fork allocation, cut, rollback, lifetime debit, idempotency, reservation, and re-root |
| Durable handoff cuts | 16 process terminations | 12 recovered the complete pre-commit state and 4 the complete post-commit state |
| Mechanism or stated abstraction | Match |
|---|---|
| Session continuity | 14/32 |
| Exact-hash all-deny | 18/32 |
| Per-generation fixed ceiling | 29/32 |
| Delegation-edge cascade | 23/32 |
| Complete authorization-succession profile | 32/32 |
| Dimension | Executed realization | Boundary |
|---|---|---|
| Authorization lineage | Every non-root successor has one authorization parent. Fork atomically partitions one predecessor’s residual and fences that predecessor. | No merge transition or multi-parent generation identity is implemented. |
| Manifest commitment | Exactly eight fields are bound: codeDigest , controlPath , enforcementConfigDigest , memoryPolicyDigest , modelRouteDigest , policyCompilerDigest , proposerId , and skillClosureDigest . | A deployment profile must add every further security-relevant surface; an omitted surface is outside this result. |
| Authority algebra | Additive nonnegative integer budgets and opaque, single-holder effect atoms. The executed budgets are actions and tokens . | No general lattice evaluator, multi-holder effect relation, or arbitrary effect normalizer is implemented. |
| Record binding | Ledger-issued, digest-bound grants, certification records, reservations, events, and receipts are checked against a frozen declared-control-root registry. | The prototype tests record binding and declared-root separation, not caller authentication or key possession; the abstract authenticated-record predicates remain deployment premises. |
| Durability | Intent, temporary state, file-image replacement, and directory synchronization around one handoff. | Atomicity evidence is limited to this file-image replacement protocol; it does not cover distributed consensus or effect-delivery atomicity. |
| Evidence bundle | Domain-separated aggregate report digest |
|---|---|
| Provider-free core | sha256:d92b3eefe1a7de48e936505c828ceff3bf83ed831a33e3bedef16cd4c3cb98ef |
| OurArk Genesis/Enoch | sha256:02e26bac1a4e05855f9be4ed750a9e38de84236f6d18c19f9d0888730e4e64f8 |
| Darwin Gödel Machine | sha256:21b26c421d36d827b38bc89cfa0df301b477ee45da4f084468de25f002c73851 |
| Line of work | Principal object | Established control | State used by this work |
|---|---|---|---|
| Earned Authority | one evolving grant holder | transition envelope and fixed effect ceiling | active generation family and allocation transaction |
| PRV | recursive activation trajectory | probabilistic risk escrow and anytime harm bound | deterministic typed effects, resources, epochs, and lifetime |
| HBHC / VERA | hierarchical credentials / delegation edges | cascading or verifiable revocation | generation cut joined with handoff, re-root, and rollback |
| OurArk / DGM | versioned descent / mutation archive | identity-bearing evolution and candidate selection | protected-effect authority assigned to current generations |
| SEVerA / RegenHarness / Bad Genius | synthesized program / versioned harness candidate | constrained outputs, evidence-gated rollout, and counterfactual validation | external succession of executable generations |
| Root-scoped quiescence | retired authorization-root carriers | pre-cut accounting and post-fence exclusion | allocation and replacement of generation principals |
| Evidence class | Object | Supported statement |
|---|---|---|
| Formal | definitions, assumptions, lemmas, theorems, proofs | conditional protocol safety for all executions satisfying the model premises |
| Reference execution | registered finite corpus, ledger, brokers, two logical adapters | implementation conformance over the executed mutation and lineage cases |
| Adversarial verification | independent checker and consistently resealed semantic regressions | checker separation and detection of the registered trace-level violations |
| Fault execution | durable crash cuts and deterministic schedules | recovery and atomicity over the exact enumerated interruption/interleaving space |
| External refinement | frozen public runtime commits, native descent or edit, fresh restart, and broker traces | field mapping and boundary behavior for the specifically executed versions |
AI Agent Security
Artificial intelligence agent security studies attacks and safeguards for tool-using, persistent, and collaborative systems across digital and physical settings.
See all 508 papers