owns: refund_resolution authority: ≤ $500 / case escalate_if: novel ∨ risk › 0.7 forbidden: issue_credit
What it does
Chapter 5 is precise about what governs a well-designed agent: not a system prompt, but a charter. "A charter — a structured governance document that defines the agent's role, decision rights, authority boundaries, and escalation paths with enough precision that both the agent and the humans overseeing it know exactly when the agent is operating inside its mandate and when it has exceeded it." The distinction is operational: "A system prompt tells an agent what to do. A charter tells it what it is: its identity, its authority, and the limits of that authority."
Sierra grounds its entire customer-facing operation in charters; each agent has explicit scope — handle returns, modify subscriptions, issue credits up to a threshold, escalate on distress. The charter "is not a script; it is a boundary condition." This is why enterprise clients pay premium contracts: "they trust that chartered boundaries hold predictably, at scale."
The Agent Charter Builder turns the framework's seven elements into a guided generator that outputs a single, valid charter YAML file — the artifact you commit to a repository, review, and version. It encodes the chapter's two non-negotiable rules. First: the charter precedes the agent. "The most common implementation failure is treating charters as documentation rather than architecture... The charter must precede the agent, not follow it." Second, derived from Chapter 6's governance discipline and Chapter 5's accountability principle ("autonomous authority must be commensurate with verifiable accountability"): no charter is active until a human signs the pull request that merges it. The tool generates the file; a person signs the merge. That is the design.
Who it's for: Architects and engineers building the Agent Plane who need charters that are real artifacts — reviewable, diffable, enforceable — rather than after-the-fact descriptions of whatever the agent already did.
Figure: The seven-element Agent Charter anatomy this tool generates and validates.
Fill the seven elements. The builder validates as you type, emits a status: draft charter.yaml, and prepares an opened pull request — it never activates a charter itself. Activation is a human-signed merge.
Agent Charters
Five Planes of Operation
Alignment Debt
Five Planes Architecture Simulator
Defensibility Stack Assessment (A.G.E.N.T.)
AI-Born Readiness Assessment
- Book 1, Chapter 5 — "Agent Charters: The Constitution of Autonomous Work" (the seven elements; charter vs. system prompt; charter-precedes-agent; Sierra; the Operating Context; authority commensurate with accountability).
- Book 1, Chapter 6 — "The Governance Layer" (the Governance Loop, escalation, Alignment Debt — why charters are enforced, not described).