Govern · For the CIO — “Can we deploy AI?”
One policy for every agent.
AI agents are becoming production software. Production software needs governance — and every new agent, framework, and protocol multiplies the surface a mistake (or an attacker) can cross. You need one place to say what's allowed, and have it hold everywhere.
Aarmos is that place. Author one policy in an 8×8 matrix, enforce it inline at every tool call, delegate with attenuation only. Any framework, any protocol.
Above the tool call sits the thing the business actually cares about: the Decision. Name the business action, declare the inputs it depends on, bind the Participants that must weigh in, and Aarmos composes their answers into one Verdict — recorded as evidence, valid only inside a bounded execution window.
Read the Field Guide chapter →How governance-first is different
Typical agent stack
- · Policy sprinkled in prompts & middleware
- · Audit logs written after the fact
- · Per-framework guardrails, no portability
- · Delegation escalates by re-prompting
Aarmos
- · One policy, enforced inline before every call
- · Decision, participants, and verdict on one signed receipt
- · Framework-agnostic — MCP, OpenAPI, deep-link, BYO
- · Delegation attenuates only — never escalates
Start here
- See it govern — 90-sec demo →Watch a policy refuse a destructive tool call, then a scoped invite let it through.
- Why governance →The problem governed execution solves, before any product detail.
- How Aarmos thinks →The reasoning model behind decisions, participants, and verdicts.
- Field Guide →The long-form reference for the whole vocabulary.
Every governed decision becomes a source of operational knowledge.
Governed execution is what produces understanding — but the two stay separate on purpose. Govern happens before an action runs; Operations observes after it ran. Operations is not a section of Govern.
- Actions & resources →The eight action verbs and eight resource types that policies and receipts name.
- Aarmos Security Policy (ASP) →The YAML authoring format, plus lint rules and CI integration.
- Decision governance →Name the business action, bind the participants that must weigh in, and record the composed verdict as evidence.
- Delegation & scoped invites →Attenuation-only sub-agents; no privilege escalation, ever.