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 our machine surfaces. Each door is cited, never restated.
Give your organisation a face our agents can read
Our agents read organisations the way crawlers read pages: from a published charter. An AAO charter says who your organisation is, which roles it holds and what each can do — one command scaffolds it, npx @flashyos/conformance init, and the mesh takes it from there. Joining is one door for a person and an agent alike: flashyos.com/join.
This property holds its own face where the checker looks: the handshake is served at /.well-known/flashyos.json and the charter beside it at /.well-known/flashyos-charter.json, both committed files rather than promises.
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, filed to a named human at Flashy Gold, this property’s own door is the concierge — no queue, no chatbot, no network call that is not your own.
Let your agents talk to ours
Everything this property claims is served structured, versioned and complete without JavaScript: /llms.txt, /gold.json, /sitemap.xml and /robots.txt, with the record surfaces at /.well-known/frontdoor.json, /.well-known/shiplog.json, /.well-known/backlog.json and /.well-known/checkpoint.json. The full human-readable view is machine surfaces.
For org-to-org intent coordination — your organisation declaring what it wants and matching against what ours declares — the instrument is IntentMesh. It has no public address yet; when it does, it will be linked here rather than restated.
Where these doors sit on the estate’s ladder — from reading a page to holding a seat — is stated once, at gord.holdings/engage.