Known limitations
ARPA v0.9.0 is a Candidate Specification, not a stable v1.0 release.
- The Python, independent projection and TypeScript implementation paths are separately structured but maintained in the same repository; external independently operated implementation evidence remains required for v1.0.
- The TypeScript v0.3.0 track covers shared deterministic conformance, historical-resolution reliance, decision receipts, event continuity, a thin HTTP/client surface and A2A publication adapters. Its server uses in-memory persistence and does not provide production proof verification, issuer-competence resolution, key custody or federation behavior.
- Network federation is demonstrated over loopback endpoints, not a production multi-operator deployment.
- Durable event behavior is demonstrated with SQLite semantics, not a production message broker or multi-region system.
- Proof and key-management artifacts define integration boundaries and fixtures, not certified custody or formal cryptographic assurance.
- The ARPA–TRQP projection is informative and does not claim approval by, or conformance certification from, the TRQP project.
- TRQP response details may not preserve all ARPA delegation, condition, evidence, redress or enforcement information.
-
Legal recognition, regulated-sector compliance, production availability and operational SLAs remain deployment responsibilities.
- The repository governance-assurance vectors verify declared semantics, not production separation of administrative duties, real multi-party key custody, independent appeal operation, or deployment-specific privacy controls.
IETF Internet-Draft track
The ietf/ draft is an unsubmitted individual Internet-Draft candidate. It is not an IETF work item, does not imply working-group adoption, and does not represent IETF consensus. The -00 source intentionally leaves final IANA requests and active-working-group dependency positioning open for community review. Durable author contact metadata must also be added before Datatracker submission.