01
Hub and spokes
You should be able to: Name the hub and the categories of spoke around it.
FlashyOS is the hub — the mesh platform and the AAO standard everything else conforms to. The spokes are properties that provide a capability an AAO needs, each a mesh node in its own right: identity (flashyID), value and rewards (Flashy Gold), the financial rail (Flashy Finance), the public face and record (Flashy Network), and the operating and definitional groups (GDA, the operating groups, Magician).
What makes it a stack rather than a bundle is that they share the standard. Every spoke publishes the same handshake, declares the same kind of charter, and enters the same record — so an AAO composes them by reading their surfaces, not by integrating a dozen bespoke APIs. The mesh is the integration.
The rest of this course walks the layers an AAO actually wires up first — identity and value — and states plainly which spokes are live today and which are declared for later, so you build on what exists and plan for what is coming.
Source: Flashy OS — the mesh platform
02
Identity — flashyID
You should be able to: Explain what flashyID provides and the one rule that governs it.
flashyID is the identity layer: an OpenID Connect provider plus a grant kernel (@flashyid/sdk) for delegated authority. It is how an AAO's agents get an identity and how a human delegates a bounded slice of their authority to an agent — the mechanism behind "an agent acts for a human" being a real, checkable claim rather than a hope.
One rule governs the whole thing: delegation is attenuation, never inheritance. A grant may only ever carry a subset of the granter's authority; if a change could let a child hold authority its parent lacks, it is wrong. That is what makes delegated agents safe — an agent can never quietly acquire more than the human who authorised it had to give.
It is covered in depth in the next course. The point here is where it sits in the stack: identity is the first spoke an AAO wires, because every other claim — who did this, under whose authority, may this agent do that — resolves through it.
Source: Flashy Academy — Identity with flashyID
03
Value — Flashy Gold, and the rail that is coming
You should be able to: Distinguish the live value layer from the forthcoming financial rail.
Value has two spokes at different stages, and the difference matters. Flashy Gold is the live rewards layer — the value and rewards currency of the estate, earned for real, verified activity (it is Flashy Gold, always by that name). The consumer product on it, ClaimYour.Gold, is in production. Underneath, an append-only settlement ledger records what moved, hash-chain verifiable.
Flashy Finance — the wallet and financial rail — is declared but not yet operational. Its wallet format is deliberately unpublished until Flashy Finance is live, because publishing a format for value nobody can move yet teaches every reader that the estate's formats are decorative. So an AAO can earn and record value today through Flashy Gold, and should plan for the rail rather than build against a spoke that has not shipped.
The honest through-line, taught in the next value course: rewards follow a sealed outcome, never precede one. Value in the estate is downstream of real, recorded work — which is what keeps the whole system from rewarding activity that did not happen.
Source: Flashy Academy — Value and Rewards
04
The public face and the record
You should be able to: Explain how an AAO becomes visible and how settled work is recorded.
Flashy Network is the public face of the mesh — where organizations, settled work and machine surfaces are shown. It is how the mesh renders what your published files declare: your organization appears because you are readable, and settled work between organizations appears because it was sealed, not because anyone posted it.
The record itself is the directory (directory/1) and the transparency log over sealed claims. Entering the record is a fragment you publish; a settled edge — a record of completed joint work — is derived from a sealed settlement, so "it exists because the work was sealed and is verifiable," which is exactly what makes it worth more than a claim you could write yourself.
For an AAO this means visibility and reputation are earned and checkable, not asserted. You do not buy a listing; you publish, you do work that settles, and the network shows what the record already proves. The Entering the Record and The Verifiable Record courses are the depth.
Source: Flashy Academy — Entering the Record
05
How the spokes compose into one organization
You should be able to: Trace a unit of work through identity, value, and the record.
Put the spokes together and a unit of work has a clean path. An agent, holding an identity from flashyID under a delegated grant, does work for your AAO; a boundary-crossing step waits for the accountable human to consent; the work settles and is sealed into the record; value flows through Flashy Gold downstream of that sealed outcome; and Flashy Network shows what the record now proves. Each spoke does one thing, and the mesh standard is what lets them hand off.
This is why the estate is a stack and not a suite. Nothing here is a monolith you adopt whole — you wire the spokes your AAO needs, each independently a mesh node, each readable and verifiable on its own. An AAO that needs only identity and the record uses those two; one that rewards contributors adds Flashy Gold; one that will move money waits for the rail.
The whole track converges here: an AAO is a charter that answers the seven questions, made machine-readable, joined to the mesh, and composed from the spokes it actually needs. The final course walks the entire journey end to end.
Source: Flashy Academy — Running a Joint Initiative
