Declaring what your organisation is, to machines

What a machine needs before it can deal with you

A human who wants to work with your organisation reads your website. An agent cannot; it needs a structured answer to "who and what is here, and how do they relate". That is the graph layer of the agentic internet, and its format, graph/1, is a vendor-neutral description of the nodes in your corner of the network — people, organisations, agents, capabilities, tools and assets — and the evidenced relationships between them. It deliberately says nothing about how good, how much, or how trusted; those are other layers’ questions. It says only what exists.

The distinction is the whole design. A graph that also carried scores would collapse "what exists" and "how good is it" into one document that no single party can honestly author, because your own view of how good you are is not evidence. Keeping the graph to existence-and-relationship makes it a thing an organisation can publish about itself without lying, and a thing a reader can consume without having to discount it.

Start from the registry, not a blank file

The graph does not ask you to invent your identity from nothing. It extends the estate’s realm/1 registry: a realm manifest already lists houses — real organisations — with their slug, domain and status, and graph/1 maps each house to an org node, carrying the house’s own handshake as the place its existence can be checked. In practice you derive your first nodes from the registry entry you already have, then add the agents, capabilities and assets that are specific to you.

$ node vendor-graph.mjs check vectors/estate-minimal.json
graph/1: vectors/estate-minimal.json: valid — 3 nodes, 2 edges, published by org/lanternworks

Ids are the estate’s throughout: a person is person/, an organisation org/, an agent agent/, and a capability is a lowercase action verb spelled exactly as an AAO charter spells it. That last rule is what lets the graph compose with the representation layer without a translation table — the verb an agent offers in the graph is the verb its charter grants it, or the two disagree and someone has to reconcile them.

An edge with no evidence is not carried

The rule that keeps the graph worth reading is that every edge carries a basis — an https URL its asserter publishes — and an edge without one is refused. An unsupported relationship is a claim, and the format does not carry claims. This is more demanding than it sounds: it means you cannot simply assert that you partner with an organisation; you publish the evidence at a URL, and the edge points at it. A reader can then follow the basis and check it rather than believe it.

No self-attestation, and no scores inside the graph

Two further refusals close the obvious loopholes. An attests edge whose asserter is one of its own endpoints is refused — you cannot vouch for yourself, because standing comes from what others assert, which is the estate’s oldest rule carried into the graph unchanged. And a set of money-and-ranking key names — score, rating, rank, reputation, amount, value, price, balance and gold — are refused at any depth, under any prefix. Reputation is a consumer’s computation over the graph; money is a separate format. A graph that let you write your own score would be a graph nobody could trust to describe anyone but its author.

The checker refuses rather than guesses everywhere else too: an unknown key not prefixed x-, a dangling reference, a duplicate id, a node whose id prefix disagrees with its kind, an edge between kinds the table does not allow — each is a named refusal with a test behind it. The effect for you as a publisher is that a document either validates and is safe to serve, or it names exactly what is wrong.

Serving it, and keeping it honest

A validated graph document is served at a well-known path on your own domain, where an agent that found you through discovery or the gateway can fetch it. The discipline that keeps it honest over time is the same one every machine surface here obeys: it is generated from the same source that produces your other surfaces, so it cannot quietly disagree with your charter or your handshake. Committed is not served — the authoritative check is a fetch of the live domain, not a file in a repository.

• The lab’s view (planned)FlashyLabs is preparing an engineering companion to this piece at https://flashylabs.com/insights/declaring-what-your-organisation-is-to-machines — planned, not yet published.
• The studio’s view (planned)The 4 Ventures thesis desk is preparing an investor-lens companion at https://4.ventures/thesis/declaring-what-your-organisation-is-to-machines — planned, not yet published.