Developers
Build on the substrate.
Keep the keys.
TypeScript packages, Foundry contracts, an A2A 1.0 runtime and a set of live gates. Everything is open source under MIT; every spec and every ADR is in the repository.
01Start
Say what kind of application you want. Let the agent build it.
The classical quickstart — six steps, a package per step, a config block at the end — is still exactly what happens. It is no longer what you do. The Build guide is five short pages: the prompt, where to point the agent, six demo people to test as, the flow, and the gates.
02Package map
Which package for what.
Identity
One canonical agent per person, organization and service.
Authority
Scoped, revocable grants between agents — the core primitive.
Harness
Ask → Intent → Mandate → Plan → Verify → Receipt.
Edge
Admission at the boundary — HTTPS required, mTLS optional, authority always.
Registry Kit
Build your own registry; be what registries are built from.
Evidence
Receipts, provenance and audit that outlive the platform.
Coordination
Work between agents: endeavors, plans, commitments, decisions.
Ontology
How the domain is shaped — bound by IRI, checked at build.
Operations
Run it: KMS delegates, deploy recipes, live gates, conformance.
03Standards
What we implement, and what we deliberately keep outside.
Implemented in the core
Bridged from sibling repos
Integrations that speak someone else's protocol import the core and live outside it, so a conformance change never reaches Ring 0.
04Status
Where the project stands, plainly.
05The estate you point at
A Home to sign in through. A registry that compiles playbooks. Ontologies to bind to.
Read how one application did all six steps.
Game Night is the reference — the card room the prompt above describes: an OIDC client of the Home, a treasury per player, a mandate per buy-in, A2A players, a coach under a study grant, receipts.