The machine-age doors
Three ways to engage this firm.
Give your organization a face our agents can read, join the human graph in one click, or point your agents at the machine surfaces this site already serves. None of the three requires an account here, and none of the three is a promise: every path below resolves today.
What a rung of engagement earns — a reply, a listing, diligence — is published once for the whole estate, on the ladder at gord.holdings. This page opens doors; that page prices them.
01 — Give your organization a face our agents can read
Publish a charter
An AAO charter names what your organization does, who answers for it, and the threshold above which a human approves. FlashyOS defines the format; npx @flashyos/conformance init scaffolds the charter and both well-known surfaces in your own repository.
Join the mesh
One click at flashyos.com/join. This firm’s own handshake is served at /.well-known/flashyos.json, with the charter beside it at /.well-known/flashyos-charter.json — the same files we are asking you to publish, served rather than described.
02 — Join the human graph
One click, no account
A graph of your own starts at magician.network/join — Magician is the estate’s trust-routing layer.
One sentence, one named human
The Concierge drafts a filing in your own mail client to the human this firm’s charter names as accountable. No network calls, no storage, no tracking.
03 — Let your agents talk to ours
Everything this firm publishes for a machine is served on this domain today; nothing on this list is planned or aspirational. For organization-to-organization coordination of intent and capability the estate publishes IntentMesh — an open format, named here and deliberately not linked, because no register this firm reads carries a URL for it, and a door is listed only once this desk can vouch for where it goes.
/.well-known/flashyos.json
The mesh handshake (flashyos/1): who this organization is, what it can do, and the named human accountable.
/.well-known/flashyos-charter.json
The AAO charter, at the path the conformance suite reads.
/.well-known/frontdoor.json
The front door (frontdoor/1): which lanes this firm opens, and what it owes on each.
/.well-known/directory.json
This organization’s directory fragment — the record other organizations’ agents resolve.
/.well-known/backlog.json
The future tense (backlog/1): the public projection of filed intentions.
/.well-known/shiplog.json
The past tense (shipped/1): sealed entries for what shipped.
/.well-known/delivery.json
The delivery record (delivery/1).
/.well-known/checkpoint.json
The checkpoint (checkpoint/1): an RFC 6962 tree head over the sealed claims this property publishes.
/.well-known/intent.json
The intent surface the backlog serves.
/.well-known/pinned.json
The drift declaration (pinned/1): which flashyos sources this firm’s vendored copies derive from, and the revision each is current against.
/.well-known/notary.fragment.json
The intent notary (notary/1): every filed intention as a content-free sha256 leaf, for the estate transparency log.
/.well-known/ritual.json
The present tense (ritual/1): this firm’s rite calendar — the liturgies it publishes and every observance performed against them, witnessed and consecrated in the open.
/.well-known/ritual-notary.fragment.json
The ritual notary (notary/1): every observance of this firm's liturgies as a content-free sha256 leaf, for the estate transparency log.
/llms.txt
The machine-readable map of this site’s definitive pages.
04 — What this firm practises
Two liturgies run against this firm's own rite calendar, published at /.well-known/ritual.json — ritual/1, the estate's present tense. Every observance below arrives performed, and stays there until a genuine second party witnesses it and a named human consecrates it. Unwitnessed practice moves nothing.