OPEN SOURCE · THE AAO STACK
The spec is open.
The network is a product.
Everything a stranger needs to check our claims or build against us ships in the open under Apache-2.0: the manifest format, the conformance suite, the SDK, the settlement verifier, the ledger rules. The services that run them live — the mesh, the books, the floor — are the product. That line is stated here once and holds everywhere.
npx @flashyos/verify
The wire formats
The standard is a handful of on-the-wire contracts, each with a version in its name and a normative home. All Apache-2.0 — fork them, ship a competing implementation, run the suite against your own register. What turns a prose spec into testable interop is a portable conformance suite: language-neutral vectors with expected verdicts, so a parser in any language can prove it accepts and rejects the same documents ours does. 7 of 12 ship one today; the rest say so rather than pretend.
The one file a stranger reads first — who you are, and where the rest of your record lives
An agent workforce declared the way a cap table declares ownership — who may do what, and who answers for it
One record per real thing, merged across an estate, with consent as a signature rather than a policy
Which lanes you open to strangers, what you ask at each, and what you owe in return
One sealed entry per thing that shipped — dated, attributed, and checkable by a stranger
What an organisation intends, published the way facts are — and decaying, so it cannot lie by inertia
One RFC 6962 root over everything you have sealed, recomputable by anyone, holding no data itself
What happened to the positions an office holds — transitions, never states, so a correction is an entry rather than an edit
How two organisations actually run a thing together — named roles, ordered steps, and the evidence each step owes
What an organisation handed over, to whom, and against which agreement
One word per property and a published commitment over the set — verified in the finder’s own browser, with no server behind it
Assets an organisation holds and the obligations it has issued against them, denominated in a unit that already circulates
Run any format's suite against your own parser: npx @flashyos/conformance yourdomain.com --level 2 grades a live domain; the per-format suites above check an implementation offline.
Packages
One secret, split across an estate, checked in the finder’s own browser
The manifest format an agent workforce is declared in
Four lines from a running agent to a visible one
The mesh as MCP tools, in one config block
A working mesh agent scaffolded into your repo
One command from a domain to a node the mesh can see and grade
Three levels, and only the third is ours to grant
Recompute every hash we publish, and check we are not lying
A lockfile for facts
A claim about you is not true until you sign it
One record per real thing, merged across an estate
What an organisation intends, published the way facts are
What you shipped, sealed so a stranger can check it
One root over everything you have sealed, recomputable by anyone
One page, one card, one claim — written by the same call that sets the title
An asset does not need its own market. It needs a unit somebody already holds
The rungs between a merged commit and a thing somebody has
A way organisations work together, as a document rather than code
The checklist for joining, so the sequence is not in somebody’s head
The estate’s shared lint base, so a rule is argued once
What happened to the positions an office holds, as a log
Which lanes you open, what you ask, and what you owe
The machine-readable front door, parsed and checked
One inference seam, several providers behind it
Repositories
The open settlement-ledger rules: append-only, signed integer minor units, hash-chained tamper evidence, idempotent writes. Apache-2.0. Fork the rules, run your own books, verify ours.
FlashyLabs/aaoThe spec's standalone public home — citable, forkable, PR-able. Going live now; until the repo resolves, the npm package above is the same code.
Also open
The brand & press kit (marks, lockups, tokens, usage rules — downloadable), and the cloneable Cloud Run deploy template every property runs on (public with the next repo debuts — no dead links here). The spec page for the format itself lives at /aao, and the naming standard at /standard. Together these packages are the open half of an agent execution protocol; the network that enforces it live is the execution infrastructure.
Every repo we open carries a sealed ⚡ STRIKE — a sha256 commitment whose preimage a careful reader can reconstruct. First verified striker per release is written into that repo's STRIKERS.md. Four strikes are live across the estate, and their preimages joined hash to one master commitment — Storm 1. Verify, don't trust; that includes us.