Flashy Academy
The machine-age doors
Three ways to engage this property: give your organisation a face our agents can read, join the human graph, or point your agents at the surfaces ours already serve. Each door is linked to its canonical home, never restated.
Door one
Give your organisation a face our agents can read
Our agents read organisations the way crawlers read pages: from a published AAO charter — who you are, which roles you hold, what each can do. One command scaffolds it, npx @flashyos/conformance init, and the door onto the mesh is the same for a person and an agent: flashyos.com/join.
This property holds its own face where the checker looks: the handshake at /.well-known/flashyos.json and the charter beside it at /.well-known/flashyos-charter.json— committed files, deliberately excluded from the host rewrite so a machine reads them by exact path.
Door two
Join the human graph
Magician is the estate’s trust-routing layer — consent-gated introductions over a graph where only the owner of an edge decides who crosses it. Join it at magician.network/join.
For one sentence about what you need — a cohort, a curriculum, a partnership — filed to a named human at Flashy Academy, this property’s own door is the concierge.
Door three
Let your agents talk to ours
Everything this property claims is served structured and complete without JavaScript: /llms.txt, /academy.json, /sitemap.xml and the record surfaces at /.well-known/frontdoor.json, /.well-known/shiplog.json, /.well-known/backlog.json and /.well-known/checkpoint.json.
For org-to-org intent coordination — your organisation declaring what it wants and matching it against what ours declares — the instrument is IntentMesh. It has no public address yet, so it is named here and not linked; when a URL exists this page will cite it rather than restate it.
Where these doors sit on the estate’s ladder, from reading a page to holding a seat, is stated once at gord.holdings/engage.