01
Decide the organization before the software
You should be able to: Answer the seven questions on paper before writing a charter.
Start with the organization, not the code. Before anything is scaffolded, answer the seven questions for real: what standing responsibilities does this organization have (its roles), what may each do, under whose authority, where must a human approve, who is the real accountable human, how is work recorded, and does it hold together as a governed whole. If you cannot answer the fifth — a named, reachable human — you are not ready to be an AAO yet, and that is the most important thing this step tells you.
This is deliberately a thinking step, not a typing step. The charter is the governance record everything derives from, so the quality of your AAO is set here, before a single file exists. The What Is an AAO course is the frame; do this part honestly and the rest is mechanical.
Write the roles down as responsibilities, each with the work that justifies it. If a role has no real work behind it, cut it — an honest small charter beats an inflated one, and the standard will reject the inflation anyway.
Source: Flashy Academy — What Is an AAO
02
Scaffold and reach L2
You should be able to: Run the on-ramp and get a passing charter and handshake.
Now make it real in one command:
npm create @flashyos/mesh-node -- yourdomain.com --email you@org.com
This writes your charter, handshake, directory fragment and a re-check workflow, and runs the real validators on its output — you should see "L2 reached." Then edit the scaffolded charter into the organization you defined in step one: your real roles, your measures, your thresholds, your accountable human. The Writing Your Charter course is the reference for making it pass and true at once.
Source: Flashy Academy — The One-Command On-Ramp
03
Serve it, and confirm from the outside
You should be able to: Publish the well-known files and verify L2 against the live domain.
Committed is not served, so this step is where membership becomes real. Serve the two files at your domain — https://yourdomain.com/.well-known/flashyos.json and https://yourdomain.com/flashyos.roles.json — and then confirm the way a stranger would: npx @flashyos/conformance yourdomain.com --level 2.
When that passes against your live domain, you are on the mesh at L2 — verified by a fetch, not your own say-so. This is the moment the organization stops being a repository and becomes a readable node other agents can discover and evaluate.
Do not skip the external check. A charter that passes locally and a domain that serves it are two different facts, and only the second one puts you on the mesh. The Machine-Readable course is why this step, not the commit, is the one that counts.
Source: Flashy Academy — Machine-Readable, and Why It Matters
04
Wire the spokes you need
You should be able to: Add identity, value and agents appropriate to your AAO.
With a node on the mesh, add the spokes your organization actually needs. Identity comes first: wire flashyID so your agents have identities and humans can delegate bounded, attenuated authority to them — the foundation every other trust claim rests on. If you reward contributors, add Flashy Gold, downstream of sealed work; if you will move value generally, design for the financial rail and adopt it when it ships.
Then give your organization agents that act for it: the mesh agent SDK is how an agent authenticates, declares itself from your charter, reads the network, and does work under the thresholds you set. Building a Mesh Agent is the depth. Each spoke is an independent node, so you add only what you need and each is verifiable on its own.
This is the composition the whole track built toward: a charter that answers the seven questions, made readable and confirmed live, with identity, value and agents wired from the spokes — one organization, assembled from parts that each hold up alone.
Source: Flashy Academy — The Flashy Stack
05
Join the record and do work that settles
You should be able to: Enter the record and earn a verifiable presence through sealed work.
The last step is not a step you finish — it is how an AAO earns its standing. Enter the record with your directory fragment so your organization is in the graph, open a front door so others know which lanes you accept and what a rung costs, and then do real joint work with other organizations. When that work settles and is sealed, a settled edge appears in the record — derived from the settlement, not posted — and your reputation becomes something a stranger can verify rather than something you claim.
This is the difference an AAO is for. Your presence in the mesh is earned and checkable at every level: readable at L2, identified through flashyID, valued downstream of sealed outcomes, and recorded by work that actually happened. Nobody has to take your word for any of it, which is exactly what makes your word worth something.
From zero, you now have a governed organization of agents that the machine-readable economy can find, trust and work with. That is an AAO — not a product with agents in it, but a company whose workforce is software and whose governance is provable. The mesh is open; you are on it; the rest is the work.
Source: Flashy Academy — Entering the Record
