Documentation
Getting-started tracks for the three parties a governed interaction has.
Only the specification is normative. These pages explain; they do not add requirements.
Where a requirement is quoted, it is quoted with its stable ID (GAA-*) and links to the exact
clause in the canonical text. If a sentence here appears to require something
the specification does not, the specification governs and this page has a defect — report it through
the proposal process.
Site owners — GAA-enable a door
You run a site or service and want governed agents to act through it: publish a discovery descriptor, stand up a deny-by-default door, and state your conformance scope honestly.
Agent builders — drive a governed door
You build an agent that acts on a person's behalf: discover a door, see only what the Mandate grants, act within it, and hand back a receipt anyone can verify without trusting you.
Humans & principals — read and verify a receipt
An agent acted in your name: what the receipt you hold actually is, and how to check it yourself — in your browser, with no key and no account.
Register of these docs
The documentation register is deliberately small: three tracks, each grounded in the specification's own requirement IDs. Reference implementations are named only as informative examples, and no vendor's product is required to implement the Standard (GAA-CTRL-8 states that any conforming implementation MAY realize a control differently).