Governed Autonomy¶
AI systems that can carry responsibility forward.¶
What happens to an AI system's commitments when its model changes, its work is interrupted, or its evidence turns out to be wrong?
Governed Autonomy is a research and evidence collection about accountable AI systems that operate over time. Its sixteen papers are accompanied by implementation and deployment evidence, an executable continuity reference, and a register of exact public assertions. It examines how systems can preserve purpose, respect limits on their authority, establish what actually happened, and finish or resolve the work they undertake.
The work is grounded in the implemented Cuttlefish and Freehold systems. Their production setting and the evidence available to readers are introduced below.
Written for researchers, engineers, and technical founders. Start with the central argument, explore the architecture, or read the papers at your own pace.
Start with the lead paper · Explore the architecture · Download the collected volume
Live systems and operational evidence¶
Cuttlefish and Freehold operate end to end for real customers. I make that statement from my responsibility for building and operating them. Their AWS implementation and workload evidence is separately dated and scoped below. Visit Cuttlefish at getcuttlefish.app to explore the public product and its operating architecture.
These systems provide the operational and experimental setting for this research. This edition retains the examination I directed on 10 October 2026 with AI assistance of Freehold engine and Cuttlefish host source, dated AWS workload observations, and authenticated image metadata. The AD8 corpus and reference analysis introduced in 2026.10.7 does not constitute a new product or infrastructure examination. The implementation evidence describes the examined image metadata and explains what each source inspection, deployment observation, and behavioral result establishes. The published inspection records retain their own dates and scope.
The research collection also includes conditional arguments, finite formal results, and proposed extensions. A running system does not resolve every theoretical construction or demonstrate every real-world guarantee. The assurance boundaries and claim register preserve those distinctions claim by claim.
A commitment survives a lost acknowledgement¶
An authorized action changes the destination. Its response is lost, and the worker exits. The obligation remains open even though the effect has happened. A successor inspects the destination, verifies the attributable result, and settles the obligation. Repeating the request leaves the controlled destination with one effect. Revoking authority prevents a new effect.
The continuity exhibit makes that sequence inspectable and executable: a separate witness counts effects, an actual process exits after commitment, and eleven checks exercise restart, replay, scope, revocation, and tampered evidence. Its guarantee is bounded by the witness's atomic contract. The disclosed source is an original teaching reference; its result is separate from production evidence.
What should survive the model?¶
A system may remember a conversation and still forget a commitment. It may complete a tool call without establishing the intended result. It may possess a credential without having the authority to use it for the task at hand.
The central proposition is that purpose, authority, obligations, evidence, and continuity need explicit institutional structure. More capable reasoning can help a system decide what to propose. It cannot, by itself, establish what the system is entitled to do or what actually happened.
- PurposeWhat future condition is being pursued?
Whose objective or internally formed mission is it? - AuthorityWho may act?
On what terms?
Who can change them? - ConsequenceWhat may change?
Who is affected?
What remains owed? - EvidenceWhat was observed?
What is established?
What remains uncertain? - ContinuityWhat must survive?
How does work resume?
How can claims be revised?
Each responsibility has its own assumptions and evidence.
Figure 1. Purpose, authority, consequence, evidence, and continuity provide five questions for examining an autonomous system.
Three contributions to examine¶
An institutional account of continuity. The lead paper develops the conditions under which identity, obligations, resources, and recourse can survive replacement of the components that do the reasoning and work. Its account includes the founders and custodians who can change the institution's rules. Read Governed Autonomous Institutions.
A map of distinct technical responsibilities. The architecture synthesis separates authored intent, application semantics, authority, effect, observation, learning, and human interaction. It distinguishes explicit source contracts, conceptual correspondences, proposed integrations, and unresolved adoption. Read Architecture of Governed Autonomous Systems.
A precise approach to evidence. A specification, an executable reference, a finite model check, an observation, and an independent review answer different questions. The collection identifies what each can support and what a stronger conclusion would require. Read Evidence and reproducibility.
Choose a reading route¶
| Time and purpose | Route |
|---|---|
| Two minutes · the thesis | This page, the responsibility map, and what exists today. |
| Fifteen minutes · architecture and a journey | The architecture synthesis, illustrated continuity exhibit, and evidence overview. |
| Full technical review | The lead paper, a topic paper below, its assumptions and counterexamples, the claim register, prior-art comparison, and review guide. |
| Read, reproduce, or share | Individual papers and the collected volume, complete review text, and the executable reproduction contract. |
The collection¶
| Theme | Papers |
|---|---|
| Institutional foundations | Governed Autonomous Institutions, Architecture synthesis, Freehold, Cuttlebone |
| Meaning and execution | MIRAGE, CSSL, IC/POAR, NTVBCD/AD8 |
| Certification and change | SEPION, RCFS |
| Application and human environment | Cuttlefish Semantic OS, Cuttlefish operating environment, CHROMATIC |
| Learning and evaluation | Experience Economy and ISE, The Reckoning, Human–LLM capability elicitation |
Read critically¶
The strongest useful review identifies a specific claim, its premises, and a case that might defeat it. Is an authority boundary complete under its stated assumptions? Does a proposed relationship preserve both systems' responsibilities? Does an observation establish the claimed outcome? Are measured results being distinguished from research hypotheses?
Use the review guide to submit a counterexample, correction, or research question.
About this edition¶
Edition 2026.10.8 corrects the authorial voice of 2026.10.7, which succeeded 2026.10.6. It retains sixteen research papers, dated evidence of implemented Freehold and Cuttlefish systems, the executable public continuity reference and the successor public-text assertion register. It retains the twelve synthetic technical investigations, public evidence catalog and Engineering Methodology page introduced in 2026.10.7. Each separately versioned work retains its own scope. Proprietary implementation details are excluded. The collection has not undergone independent peer review; operational presence and the public reference do not establish one proved integration of all the named architectures.
The sources and method, bibliography, and author statement explain the basis of the work, its relationship to prior scholarship, and the assistance used in preparing this edition.
The collection is available for reading and review with all rights reserved. See rights and permissions and third-party notices.
Technical investigations in the successor edition¶
Research Depth & Proof connects twelve falsifiable investigations to all sixteen research areas. Engineering Methodology describes sole-human responsibility, substantive AI collaboration and the evidence boundary. Edition 2026.10.8 documents the preserved predecessor, corrections and separate release requirements.