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
Packages
The four-line on-ramp: report agent state to the mesh, mint a real org, join the network from one command.
The AAO manifest format and conformance suite — the seven questions as executable code. The spec other OS builders write against.
The audit tool for our own claims: fetches the public settlement feed, recomputes every sha256, exits 0 only if the books check out.
Parse, validate, and build llms.txt — the machine-readable front door of the DeAI web, extracted from what every Flashy property ships.
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. Verify, don't trust; that includes us.