Start here

ARPA is easier to navigate when you begin with the decision you need to make, not with the repository directory structure.

First decision

You need to… Go to Primary outcome
Understand why this repository is broader than a protocol Agent Governance Lab Problem statement, lab scope and review posture
See the open research questions Research Agenda Bounded research questions and near-term increments
Understand the wider architecture Agent governance reference architecture Component boundaries and separation rules
Examine planned experiments Lab Experiments Hypotheses, evidence targets and promotion path
Contribute external implementation evidence Independent implementation guide Evidence package and independence language

ARPA journey

You need to… Go to Primary outcome
Understand ARPA’s trust and authority model 1. Understand ARPA Correct conceptual boundaries and module selection
Implement or evaluate code 2. Build ARPA Working protocol implementation
Test a conformance or release claim 3. Assure & Conform Machine-verifiable assurance evidence
Deploy or govern a registry 4. Operate ARPA Operational controls and readiness evidence
Connect A2A, TRQP or another system 5. Integrate & Interoperate Explicit protocol-boundary mapping
Contribute, release or review governance 6. Govern & Contribute Reviewable change-control and repository evidence

Version boundary

  • Current normative project baseline: ARPA Candidate Specification v0.10.0.
  • Historical provenance: Candidate v0.9.0 plus the adversarial-hardening, PP-01, PP-02 and PP-03 amendment artifacts remain retained for auditability; they are no longer meant to be manually overlaid to determine current requirements.
  • Current implementation release line: v0.9.5 remains the independently versioned implementation and cross-runtime interoperability release. The GitHub v0.10.0 release is a Candidate Specification consolidation release, not an implementation v0.10.0 claim.

Guides and implementation code do not silently redefine normative requirements. Optional profiles become normative only when that profile is claimed.

Developer shortcut

If you are here to build something, start with Build ARPA, then run make release-check-all and review the evidence described in Assure & Conform.

For every rendered document and historical release note, use the Documentation catalogue.

Standards engagement

ARPA maintains a separate IETF Internet-Draft authoring track for the interoperable protocol core. The current published revision is draft-sankarshan-agent-registry-protocol-04, published on 29 September 2026. It is an independently versioned publication surface and does not replace the ARPA Candidate Specification.

For future IETF work, use two explicit baselines:

  • IETF comparison baseline: published -04, which is immutable.
  • Current ARPA source baseline: Candidate v0.10.0, from which protocol-core propositions may be selected through explicit disposition.

Project-only governance, conformance, assurance, deployment, lab and implementation material does not enter a later Internet-Draft automatically.

Use this path when reviewing ARPA for IETF protocol extraction, revision deltas, IANA requirements, or overlap with adjacent IETF work.

Operational assurance experiments

The operational assurance evidence disposition explains how the optional observation, dependency and composite reliance test profiles relate to ARPA’s authority control plane, and where independent evidence is still missing. It is an informative integration review, not a new protocol baseline.


Agent Registry Protocol documentation. Specification text and documentation are licensed as stated in the repository NOTICE and license files.

This site uses Just the Docs, a documentation theme for Jekyll.