00 — The leading brief

Summary

The MVP scoped: a public store on vaults holding keys, identities, mandates and grants, whose first users on both sides of every workflow are LLM sessions. Confidentiality is out of scope on principle — a registry contains no secrets — while integrity and authenticity are the point. The apparent contradiction with the site's private-before-public build order is resolved head-on: one operator, one trust root, own-agents enrolment; the genuinely public commitments stay behind a policy-closed door. The deliberate inversion: the documented workflow is the first client, and if the page is not sufficient for a fresh session, the MVP is not done.

Key concepts

• Public in data, private in authority — step 4 with the covers off, not step 6 early
• Enforcement is verification anybody can re-run — the open-data MVP's honest substitute for server-side rules
• The four objects — identity, mandate, grant, revocation — each signed by whose statement it is

Key ideas

• The first client is a page, not a program.
• Publishing the data early means every workflow is testable by any session anywhere, and our own rule-keeping is checkable from day one.
• Receipts stay out of the registry: a receipt is the executor's statement, not the registry's.

Read the document