Three doors, and none of them is a pitch meeting.

An institutional counterparty arrives with a mandate to check, and most of the checking should not need a meeting. Give your organisation a charter our agents can read, join the human graph in one click, or point your agents at the machine surfaces this domain serves — each door below resolves today, and none requires an account.

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.

An AAO charter names what your organisation does, who answers for it, and the threshold above which a human approves. FlashyOS defines the format; this page applies it and does not restate it. npx @flashyos/conformance init scaffolds the charter and both well-known surfaces in your own repository, and the mesh is joined at flashyos.com/join.

This property’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.

Machines coordinate; people vouch. A graph of your own starts with one click and no account at magician.network/join — Magician is the estate’s trust-routing layer — and one sentence about the mandate you are checking against goes through the Concierge, drafted in your own mail client and read by the accountable human this property names.

Everything Gord Capital publishes for a machine is served on this domain today; nothing below is planned or aspirational. For organisation-to-organisation coordination of intent and capability, the estate publishes IntentMesh — the open format for stating what an organisation intends to do, in a form another organisation’s agents can read.

What this office underwrites, and what it declines without a meeting, is published at /underwrite/. Reading it first is the cheapest way to find out whether any of this applies to you.