01
Adopt
Read the standard, pick the lanes that apply, encode them in your team's review bar. Free, no subscription required.
▸ Open · public · free to read · free to adopt
The standard, in public.
Where it lives
The canonical text lives on GitHub at aadm-standard. This page is your directory to its sections — not a fork.
AADM is an open standard. Your engineers read it, your security team reads it, your partners read it. Changes land via pull request like any mature open project. The hosted MCP packages this text into tools your agents load — nothing more.
Six sections. One body of work.
Names match the standard repo. Click any section to open it on GitHub. The MCP loads the same text on demand via fetch_auth, fetch_seam, and role_guide.
If the UDALI band names are new to you, the agentic engineering page walks all twenty-two layers with what lives in each and the judgment call agents tend to get wrong there.
- A
Workflows
The three lanes — Navigator (delivery), Investigator (defect), Sentinel (assurance) — with their stage spines and entry/exit gates.
When to read
Read first. Workflows are the spine of everything else.
- B
UDALI
Unifier, Designer, Adapter, Logician, Integrator — twenty-two layers in five bands, the vocabulary for naming where work belongs in your stack.
When to read
When scoping a feature or tracing a defect across layers.
- C
AUTH catalog
Numbered authorization controls (AUTH-XX) with descriptions, applicability, and enforcement boundaries.
When to read
Any time authorization is in scope — the agent loads these via fetch_auth.
- D
SEAM catalog
Numbered handoff archetypes (SEAM-00 through SEAM-15) with normalization, dispatch, and persistence patterns.
When to read
Anything that crosses a boundary — assurance binds evidence per seam.
- E
Doctrine
Role guides, troubleshooter mode, audit programs, attestation examples — the body of guidance the MCP loads on demand.
When to read
Reference material the agent pulls slice-by-slice via fetch tools.
- F
Templates
PRD, BIS, audit outlines, slice plans, evidence binders — the document shapes AADM tools emit.
When to read
When writing the kinds of documents AADM helps produce.
Three ways to use it. One way to change it.
02
Cite
Reference AUTH-XX, SEAM-XX, and UDALI bands in your PRs, audits, and incident reports — give your engineering language a shared spine.
03
Wire
Subscribe to the hosted MCP so your agents load the same text on every turn — without you maintaining a fork.
Change it
The standard repo accepts pull requests. Open one for additions, corrections, or new section proposals. Big changes start as issues so the community can weigh in before code review.
The hosted MCP tracks the standard's published versions — your subscription doesn't bypass the process.
Read it. Adopt it.
Wire it.
The text is free. The subscription is for the running service that streams it to your agents on every turn.