Build ARPA
This is the primary developer journey. Start with the smallest executable surface that matches your role, then expand only when the required governance semantics demand it.
Fastest paths
| Goal | Start here | What you should produce |
|---|---|---|
| Run the repository locally | Quickstart | Passing schema, vector and service checks |
| Stand up a pilot | 15-minute quickstart | Pilot-readiness evidence |
| Choose an implementation shape | Implementation selection guide | Explicit supported modules/profiles |
| Implement from the specification | Implementor guide | Protocol-conformant behaviour |
| Use TypeScript/Node.js | TypeScript implementation | TypeScript conformance and interoperability evidence |
| Understand the supplied Python service | Reference implementation architecture | Reference service understanding, not normative behaviour |
Machine-readable sources developers should prefer
schemas/for validation contracts;registries/for governed values and codes;openapi/arpa-openapi.yamlfor HTTP surface definitions;asyncapi/arpa-events.yamlfor event contracts;- Conformance guide for executable behavioural expectations and links to the governed test-vector corpus.
Do not copy constants or behavioural assumptions from another implementation when a normative artifact or conformance vector exists.
TypeScript developer path
cd typescript
npm install
npm run release-check
To run the local TypeScript HTTP service:
npm run network-server
The TypeScript implementation is deliberately repository-artifact driven and behaviourally independent from the Python reference implementation.
Next
After local implementation succeeds, continue to Assure before treating the implementation as interoperable or release-ready.