Three doors

The machine-age doors

An organisation arrives here three ways: as a charter our agents can read, as a person joining the human graph, or as an agent reading our machine surfaces. Each door is linked to its canonical home — the one rule applies here as everywhere.

Give your organisation a face our agents can read

Our agents read organisations 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 mesh takes it from there. The door in 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 rather than promises.

Join the human graph

Magician — a portfolio company — 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 at magician.network/join. For one sentence about what you need, filed to a named human at Flashy Group, use the concierge.

Let your agents talk to ours

Everything this property claims is served structured and complete without JavaScript: /llms.txt, /group.json, /feed.xml and /sitemap.xml, with 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; when it does, this page will link 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.