Outreach, community and advocacy — with a human gate on anything public.
For teams whose growth runs on relationships — communities, partners, advocates — who want the follow-ups never dropped and the public voice never delegated past its gate.
Everything below — every role, purpose, measure and gate — is rendered from AMBASSADOR_OS in @flashyos/aao at build time. This page cannot drift from the shipped template.
“Relationships at scale, without any of them feeling automated.” — 5 standing responsibilities, each a role that outlives whoever holds it. Capabilities name actions, never departments; gates sit where a mistake would hurt, not everywhere.
| Role | Purpose | Capabilities | Approval gate | Measure |
|---|---|---|---|---|
| outreach growth | Finds the right people to talk to and opens the conversation. | research · draft · schedule | human at MEDIUM+ | Replies per hundred approaches |
| relationships support | Remembers every prior conversation so nobody is treated as a stranger twice. | record · summarise · remind | no gate declared | Contacts with a recorded next step |
| events operations | Runs the logistics of getting the right people in one room. | schedule · invite · track | human at MEDIUM+ | Confirmed attendance against invited |
| content growth | Writes what the organization says in public. | write · publish | human at MEDIUM+ | Inbound conversations attributable to published work |
| coordination governance | Settles which role owns an ambiguous request, and keeps this charter true. | plan · approve | no gate declared | — |
accountableTo: you@example.com — the template ships the placeholder on purpose; conformance fails it until a real human is named. That field is the whole point. Escalation: coordination.
The outreach role researches, drafts and schedules with a MEDIUM gate, and its measure is replies per hundred approaches — the relationship work that dies in a founder’s drafts folder becomes a role that reports its own hit rate.
The relationships role records, summarises and reminds, measured on contacts with a recorded next step — so no thread ever ends with silence nobody chose.
The content role writes and publishes at a MEDIUM threshold, measured on inbound conversations attributable to published work. Drafting scales infinitely; publishing waits for the human whose name is on it.
Copy the template, change every field — a charter describing work nobody does is worse than none — then gate your CI on validateCharterDocument and static conformance. The full path — validation, the CI conformance gate, the JSON Schema for any language — lives on the builder hub; the format itself on the AAO spec page, and the naming rules every role above passes at /standard.
These are starting points, not defaults to ship — a charter describing work nobody does is worse than none. When yours validates clean, the network is waiting.
Start building