Enterprise
What is an AAO charter, and what does a regulated firm put in one?
The governance record every other machine surface derives from — checkable at the domain, not just committed to a repository.
The answer
An AAO charter is the manifest by which an organisation declares itself to machines — its roles, the human it is accountable to, and the approval gates on each role — where AAO expands to Agentic Autonomous Organization. A regulated firm puts in it capabilities named as verbs a policy can enforce, approval gates only where a mistake would hurt, and a real reachable human at the top, because a charter without one is refused.
The two conventions that carry the value
Capabilities name actions, not departments: deploy and review, never engineering — a capability that names an org unit can never be enforced, because there is no action to check an agent against. Approval thresholds go where a mistake would actually hurt, not everywhere: uniform gates are how governance becomes theatre people route around, so a read-only role needs none and anything touching money needs one at every level.
Answered, not asserted
Conformance is checked by reading the charter from one well-known path and nowhere else — a charter committed but not served where the checker reads is not held, however correct it is. A top-level key that is neither a spec field nor extension-prefixed fails every static question, a role name is length-capped, and a family with no genuine role is left empty rather than filled, because inventing a role to fill a family is the roster inflation the format exists to stop.
The underlying concept is defined canonically at The AAO charter — FlashyOS. This page answers the build question; that page answers the “what is it” question.
Talk to the practice
Tell us what you are trying to build and what has to be true for it to work.
Contact