Agent Statecraft · Operational Doctrine

The practice of
governed autonomy.

Agency Papers make the constitutional argument. Agent Statecraft is the operational layer — how you build the control plane, which enforcement patterns hold at scale, and what the evidence chain looks like in production. Technical depth. Real implementations. Verifiable claims.

6
Published
6
Planned
3
Domains
4
Tracks
The Gap This Series Fills

From constitutional argument
to working system.

The AI safety field has produced sophisticated arguments about why governance is necessary. What it has produced far less of is concrete architectural guidance on how to build governance systems that actually work in production — that survive contact with real agents, real tools, and real operational pressure.

Agent Statecraft closes that gap. Each article in this series is grounded in a working implementation — Vigil, FlightLaw, Chronicle Quest — and addresses a specific architectural question practitioners face when building governed AI systems.

The AgentVector framework →
Questions this series answers
How do you enforce governance at the point of action, not the point of deployment?
What does a deterministic control plane look like in TypeScript? In Swift?
How do you prove two governance kernels in different languages enforce the same Laws?
What is the right data structure for an audit trail that survives regulatory scrutiny?
How do you build a resource budget model that makes agents degrade gracefully?
What does jurisdiction design look like for a domain the Codex doesn't name yet?
Curriculum

Read in sequence or by track.

Articles build on each other. The Foundation track establishes the architectural argument. Implementation shows it across three domains. Patterns extract the repeatable methods. Field Guides are operational references you can work from directly.

Foundation
Implementation
Patterns
Field Guide
07
Budgets, Not Permissions
Why resource governance is fundamentally different from access control. Law 4's budget model changes how agents degrade — gracefully and traceably — instead of failing silently.
Planned
08
Desktop Agents and the Sidecar Problem
Agents with shell and browser access can execute in tools that weren't designed for governance. How Vigil operates as a sidecar — enforcing boundaries without modifying the tools themselves.
Planned
09
Audit as Architecture
Event-sourced governance and the replay guarantee. Why hash-chained evidence logs are the only audit trail that survives scrutiny — and how to build the replay invariant in.
Planned
10
The Pilot Who Never Blinks
Governing autonomy in safety-critical flight systems. What aviation's existing crew resource management doctrine teaches about authority gradients — and why it maps directly onto governed AI.
Planned
11
Jurisdiction Design
How to compose Laws for a new operational domain. A structured approach to identifying your invariants, specifying your enforcement rules, and writing the conformance fixtures that prove they hold.
Planned
12
Your Jurisdiction
A complete worked example of building AI governance from scratch. One domain, step by step: from identifying what must be deterministic to shipping a verifiable control plane.
Planned
Domain Coverage

One pattern. Three operational contexts.

The governance architecture doesn't change between domains. Only the Laws composed within it differ. These are the three domains where Agent Statecraft articles have been written or are underway.

01
Desktop Agents
Vigil · TSVector

Autonomous agents with shell, browser, and filesystem access. The canonical governance challenge: continuous action at machine speed, with a composition problem that per-action evaluation cannot catch.

Boundary · Resource · Authority
2 articles
02
Autonomous Aviation
FlightLaw · SwiftVector

Drone operations under FAA Part 107. The regulatory context makes the governance case explicit: deterministic safety boundaries are not optional when certification requires them.

Spatial · Resource · Authority
2 articles
03
Narrative AI
Chronicle Quest · SwiftVector

Human authorship as a formal governance constraint. AI may draft prose; it cannot decide fate. Character mortality and plot resolution are human-only state transitions with audit trails.

Persistence · Authority
1 articles
The Two Layers

The argument and the architecture.

Agent Statecraft is the operational counterpart to Agency Papers. Agency Papers establish why behavioral oversight cannot scale and what architectural governance must replace it. Agent Statecraft shows how to build that replacement — the control plane, the enforcement kernel, the evidence chain.

Read both in parallel: Agency Papers for the constitutional argument, Agent Statecraft for the engineering discipline.

Agency Papers →
Agency Papers
Constitutional argument
Why deterministic governance · What behavioral oversight misses · The architectural contract
grounds
Agent Statecraft
Operational doctrine
How to build the control plane · Which patterns hold · Verifiable enforcement across domains