Who publishes
The registry
Organisations serving intent/1 at their well-known path. Listing is voluntary, free, and verifiable by anyone — the registry never contains a fragment, only the URL where yours answers. A registry that embedded copies would go stale and be believed.
The number that matters
Independent adopters — organisations with no financial relationship to the steward's group: zero. That number is printed here, at its true value, because it is the only adoption evidence that counts. A portfolio company adopting its investor's format tells you about the relationship, not the format; captive adoption is recorded separately in PILOTS.md and never added to the headline. The day this line changes, it will name the organisation and link the URL you can fetch yourself.
Being listed
Serve /.well-known/intent.json, then open a pull request against
registry.json adding
{ "org", "domain", "listed" }. The check is a fetch:
npx intentmesh registry verifies every entry, CI runs it on every change, and a
listing that stops serving is caught by the same command that let it in. No fee, no review call,
no account — and delisting yourself is the same pull request in reverse.
Why a registry at all
intent/1 deliberately defines no discovery protocol — a merge is over the fragments you already know about. The registry is the bootstrap: the smallest possible answer to "who can I merge?", holding nothing but pointers, replaceable by anyone who keeps a better list.