01
One mandate.
Two lifetimes.
The spike investigates and implements compliance. The edict keeps leadership reviewing the news after that work is delivered.
Replay the split ↗From intent to governed systems
AGI Reactor
A Safe, Governable Reference Architecture for Enterprise AGI
Policy-governed service orchestration is all you need.
From the original drawing 13 September 2026Open the source +
The whole system.
Language becomes commitments. Definitions compose execution.
Swipe the diagram to follow the system →
Tickets preserve work. Edicts preserve direction. Typed bindings connect reusable definitions to agents; governed services turn their actions into results.
Follow one mandate ↓A mandate becomes a system.
Watch the factory. Select any component to inspect its role.
WorkAuthorityEvidence
Spike ticket
“Design and implement Compliance for the AI Kill Switch Act.”
Edict
“And moving forward, get the right leaders together monthly to review your AI Compliance News Report.”
Example source: H.R. 9917, introduced text ↗. The spike establishes current status, applicability and requirements; the title alone creates no compliance conclusion.
READYIllustrative architecture
One dictation. Two durable commitments.
The compliance request becomes a spike ticket. Monthly leadership review becomes a standing edict.
Illustration only · no model calls, meetings or deployments.Download the example output ↓
Inside the example
Follow the commitments.
One mandate.
02
Compose the capability.
Bind policy, reusable patterns and relevant skills. Add current work and permitted sources. The resulting frame gives the agent its place and purpose.
Watch composition ↗03
The review becomes
part of the system.
A sourced report reaches the right leaders each month. Decisions create owned follow-up work. That work informs the next review.
Follow the continuing loop ↗What it knows.Sources, context and uncertainty.
What it owes.Tickets, owners and acceptance.
What it may do.Identity, policy and scope.
What it can afford.Reserved resources and limits.
02 / The safety foundation
A reference monitor’s safety is as strong as its policies.
Anderson’s reference monitor mediates protected access. Its implementation must resist tampering, be invoked for every protected reference and permit thorough analysis. [1] Saltzer and Schroeder sharpen the obligation: explicit permission, complete mediation and least privilege. [2]
The Reactor applies this boundary to service calls. An agent proposes; the owning service admits or refuses. Policy, trusted facts and enforcement must all hold. Changes to those controls require their own authority.
“Safe” names the safeguards in this reference design. Their effectiveness depends on qualified implementations, adequate policies and declared host assumptions. The animation demonstrates the intended mechanism; it does not certify a deployment.
03 / The public language
Shared meaning.
Accountable governance.
PanSigna.org—“all signals”—is proposed as a public consortium for encoding a public intermediate-representation ontology, with an index and wiki.
Public identifiers, types and relations make service contracts and policy profiles inspectable across implementations. W3C OWL 2 provides an established semantic foundation. [3]
Internet Society stewardship is a proposed mandate requiring an agreed charter. [4] Public definitions do not grant control over private deployments. Institutions adopt profiles; operators remain accountable for enforcement.
Persist obligations.
Replace execution.
Objects, links and messages carry the meaning. Typed service calls do the work.
One assignee. Durable work.
A ticket has zero or one assigned agent. Attempts can change; at most one is current. The resource owner still handles concurrent updates.
Context carries its sources.
Owned records → permitted views → composed frames → attributed evidence. Types and bindings connect them. Retrieved instructions never widen authority.
Uncertainty stays visible.
An operation keeps its identity across crashes. A lost reply may leave UNKNOWN. An authorized reconciler owns the gap; blind replay stops.
The animated journey, step by step
- One dictation. Two durable commitments.
“Design and implement Compliance for the AI Kill Switch Act.” becomes a spike ticket. Monthly leadership review becomes a standing edict.
- Bind the right knowledge and rules.
The spike resolves the bill text, status and applicability. Policy, control templates and assurance examples bind to the task; the edict defines the continuing review.
- Compose the agent’s working frame.
The compositor assembles the brief, verified sources, relevant skills and pending work. Legal, security, engineering and the accountable AI owner are proposed review roles.
- Produce a control candidate.
The agent drafts service code, tests and requirement mappings. News feeds a sourced AI Compliance News Report; findings can create linked follow-up tickets.
- Check the work. Enforce the boundary.
The illustration admits a reviewed candidate only within its policy and release scope. A denied caller cannot cross the same boundary. Actual compliance needs qualified controls and evidence.
- Deliver now. Keep reviewing.
A governed release can deliver the control. The edict continues as a monthly review of the AI Compliance News Report, with an owner, the right leaders and linked decisions.
The working vocabulary
- Object
- A stable identity, type, revision and owner. Its storage representation can change.
- Link / binding
- A typed relationship. A binding applies an exact definition to a scope; protected changes use the owning service.
- Message / invoke
- Attributed communication; a typed request through an authenticated service contract.
- Edict / policy
- Enduring direction; enforceable rules require authorized promotion, versioning and activation.
- Skill / agent type
- Reusable procedure and composed profile. Neither is an identity or permission grant.
- Compositor / frame
- Permitted context assembled with intent, constraints, sources and pending effects.
- Reaction / routine
- An event or schedule invokes governed work. The monthly review continues under its adopted edict.
- Operation / evidence
- Immutable effect intent and attributable outcome. Original caller, target and arguments survive takeover.
The reference stack and its evidence
| Role | Reference | Contract |
|---|---|---|
| Communication | NATS / JetStream | Calls and durable notifications; neither grants assignment. |
| Owned state | PostgreSQL + control service | Transactional records, custody, revisions and outbox. |
| Authorization | Cedar + service enforcement | Proposed integration: validate schemas and refuse evaluation errors. |
| Execution | Compositor, workers, adapters, supervisor | Bound context, egress, resources and independent stop control. |
| Evolution | Governed release controller | Isolated candidate → observed canary → staged traffic; retain a checked hot fallback. |
These are reference choices and contracts, not a qualified deployment. The existing RFC-001 exercises one local HTTP/SQLite crash-and-restore case. Its guarded trace records one effect and zero duplicates; the broken control duplicates the effect. It does not exercise this compliance scenario.
A deployment must qualify containment, concurrent admission, policy adequacy and recovery on its actual stack. Restore begins with new effect admission held until stale execution, unresolved effects and newer authority changes are reconciled.
Sources, scope and citation
- James P. Anderson. Computer Security Technology Planning Study, Volume I (1972), §§3.2.1–3.2.2, pp. 8–10. Original report ↗
- J. H. Saltzer and M. D. Schroeder. “The Protection of Information in Computer Systems” (1975), §I.A.3. Primary source ↗
- W3C. OWL 2 Web Ontology Language: Document Overview, Second Edition (2012). Recommendation ↗
- Internet Society. Policy Development Process. Stewardship context ↗
- U.S. Congress. AI Kill Switch Act, H.R. 9917, introduced in House, 23 July 2026. Illustration source ↗. The introduced text is a research input, not a finding of present legal obligations.
- Core NATS · JetStream · PostgreSQL transactions · Cedar evaluation semantics.
The design assumes trustworthy administrative roots and correctly enforced isolation. It addresses bounded operational hazards; it establishes neither general alignment nor protection from compromised root authority. Institutional participation and the compliance implementation shown are proposals.
Smithright, Ryan. AGI Reactor — A Safe, Governable Reference Architecture for Enterprise AGI. AEGISES, draft 2.0, 14 September 2026. Version permalink · BibTeX · CSL-JSON.
Animation source: TypeScript · CSS · Archived previous edition.
Credits
Internet Society, IETF, W3C, MANRS
Root Stewardship, International Security, & Standards Foundations
Academia & Sciences
Computer Science, Computational Linguistics, Compute Primitives, Encodings, Compiler Engineering, Ontology Engineering, Type Theory, Calculus, Data Science, Information Theory, Language Models, Public Benchmarks, Microkernels, OS Engineering, Network Engineering, Network Protocols, Encryption, IPC, IO, API Engineering, Control Theory, Data Engineering, Model Routing, Enterprise Software Architecture, Middleware Architecture, Internet Exchange Architecture, Computational Neuroscience, Cognitive Science, Artificial Life, Ethics, Philosophy
Peter Singer, AI Safety Community, & Effective Altruism
Ethical Rigor, Moral Courage, Inspiration
The Open Source Community, Libraries, Public Educators, & other Free Education Sources
Giants and Legends ALL!
Assembly, Compiler, C, C++, Rust, Forth, POSIX, Unix, Python, & Language Communities
Giants and legends ALL!
Andrew Tanenbaum & Minix
OS Force, Inspiration, Rigor
Linus Torvalds & Linux Foundation
Kernel Force, Git Force, Foundations
Cloud Native Compute Foundation
Stewardship, Foundations
Ben Goertzel
AGI Foundations, Inspiration
Foundations, Kubernetes Force, Thought Leadership, Standards Force, Equanimity
Anthropic
Moral Courage, Thought Leadership, & Code Force
OpenAI
Code Force, Thought Leadership, Moral Courage
Chris Lattner
Inspiration, MLIR Force, Foundations
Stanford University
Computational Linguistics Thought Leadership
ETH Zurich
Inspiration, Systems Architecture Force, FPGA Force!
James Anderson
Inspiration, Reference Monitor Foundations
Ludwig Wittgenstein
Language Game Theory
Gottfried Leibnitz
Characteristica Universalis, Calculus, Inspiration
Steve Jobs & Apple
Mac Force, Design Inspiration, Posthumous Review
Elon Musk & Grok
Foundations, News & Research Force, Veracity Balancing
Jensen Huang & NVIDIA
Compute Force, Foundations
Andrej Karpathy, Ilya Sutskever, John Carmack
Inspiration, Foundations
DeepSeek
Open Source Foundations, Thought Leadership
Synadia & NATS
Inspiration, Foundations
Proton.me, Signal Foundation
Moral Courage, Security Foundations
Family, Friends, & Communities
Invaluable!
Kevin Carl Smith
Moral Courage, Foundations, Support
Daniel Faggella & Emerj
Potestas, Persistence, & Flame, Adversarial Agency
Clark Becker
Support & Friendship
Jeff Buhrt
Mentorship, Inspiration
Personal Foundations
Accenture, MuleSoft, SalesForce, Purdue University, Springboard
Other Industry, Academic, & Thought Leadership Foundations
Alan Turing, Bell Labs, Microsoft, Oracle, IBM, Meta, Huggingface, OpenHands, Adobe, McKinsey
Mythos & Inspiration
Isaac Aasimov, Ray Kurzweil, The Wachowskis, James Cameron, The Primeagen, Cormac McCarthy, Jorge Luis Borges
The World's Fair & Olympics
Inspiration, Sportsmanship, Moral Courage, Diplomacy
USA
Foundations, Tubes, Silicon Valley
China
Foundations, Make Force
EU
Foundations, Legislation Force
Nova Mente
Inspiration, Partnership, Mythos
Chief & Jupiter
Beast Force, Inspiration
and so many more giants and trim tabs...