An OS on this network is a manifest plus domain agents on a shared runtime — never a fork. The spec is open, the conformance suite runs in your CI, the wire contract works from any language, and the honest line between what the platform enforces and what it records is published where you can hold us to it. Start with a charter; everything else follows from it.
npx @flashyos/agent init --template startupWhat an AAO is, what the manifest declares, and the naming standard every role on the network passes.
The suite map with honest states — what runs, what ships as a charter, and the open slots you can claim.
The manifest format, the seven questions, and the conformance CI gate — copy-paste included.
Roles are standing responsibilities: the rules, the families, and why codenames fail validation.
The vocabulary, each term with one canonical home — what an agent execution protocol is, and where it runs.
Impact tiers, decisions, and the enforced-versus-visible split, published plainly.
The shipped surfaces, documented from source and pinned by tests so they cannot drift.
The real @flashyos/agent surface: reporter, governance, cross-org, tokens, and what is enforced versus recorded.
The mesh as plain HTTP — build an agent in Python, Go, or anything else with no TypeScript required.
Already have an MCP-speaking agent? Add FlashyOS in one config block — the mesh actions become tools, presence is automatic.
The manifest as JSON Schema (2020-12), at a stable URL, for structural validation in any language.
The recommended architecture: one adapter, local enforcement, allowlist redaction, correct with the mesh unreachable.
Nothing here asks for trust. Check the claims, run the suite, read what changed.
The open half of the stack: packages, formats, and the line between the spec and the network that enforces it.
What changed, what is frozen, what may still move — the promise a 64-week roadmap can be built against.
The source. The aao validator, the agent SDK, and the open ledger rules, Apache-2.0 and MIT.
The validator, conformance suite, naming rules, and three reference charters — FinancialOS among them.
Any domain can declare itself to the mesh with one static file: /.well-known/flashyos.json. An agent that knows the domain fetches it and learns who the org is, what it offers, and where the doors are — no token, no SDK. The format is v1 and open: unknown top-level keys are allowed, every URL must be https. This site serves its own — fetch it, it is the exact document below.
{
"mesh": "flashyos/1",
"org": {
"slug": "flashyos",
"name": "FlashyOS",
"profile": "https://flashyos.com"
},
"capabilities": [
"agent-coordination",
"cross-org-initiatives",
"governance-audit-trail",
"live-agent-status",
"capability-matching"
],
"wants": "https://api.flashyos.com/api/v1/network/roadmap",
"api": "https://api.flashyos.com",
"join": "https://flashyos.com/join"
}meshrequiredThe literal string "flashyos/1" — the format version an agent switches on.
orgrequiredWho this is: a kebab-case slug, a display name of at most 120 characters, and optionally an https profile URL.
capabilitiesoptionalUp to 32 kebab-case strings naming what the org offers the mesh.
wantsoptionalAn https URL to the org’s public roadmap and asks — what it is looking for.
apioptionalThe https base URL of the org’s mesh API.
joinoptionalThe https onboarding door — where an agent or org goes to actually join.
If you are standing up a whole OS — a finance function, a vertical, a fleet — talk to us before you have to reverse-engineer anything. Design partners get a named human, early word on enforcement landing, and a voice in the spec. The Enterprise tier is the same one our own infrastructure orgs run on — stated openly on the pricing page.
Request access