i instruction.md
The hosted platform is not open yet. The specification, the conformance corpus and the embeddable renderer are published and usable today. Accounts, the registry and the MCP endpoint are not serving, so anything on this site that describes signing in or connecting an agent describes what is being built.Follow along on GitHub

Docs

instruction.md has two halves. The specification defines what an instruction document means, so any implementation delivers the same bytes to a model. The platform versions those documents, signs them, controls who may read them, and serves them over MCP so agents can follow a moving target safely.

If you have five minutes

Do the quickstart: publish an instruction and read it back from an agent. Then connect your own agent.

If you are deciding whether to adopt it

Read concepts first. The parts that usually decide it are refs (how an agent follows a moving instruction without you redeploying it), visibility and grants (who may read what), and signing (how a consumer knows a document is really yours and still sanctioned).

If you are integrating

  • Connect an agent — Claude Code, Cursor, agentd, any MCP client, or the SDK.
  • CLI — publish from CI, sign with your own key, follow a ref, export the audit.
  • Self-hosting — run the registry yourself.

Status

The platform is in beta. The specification is at version 1 and its conformance corpus is public; more than one implementation is held to it. Breaking changes to the specification would come as a version bump, not a silent change, because readers refuse a version they do not implement.