JARVIS Reference Stack
First-party OSS reference stack for ARP Standard
JARVIS is the first-party open-source implementation of ARP Standard v1 (node-centric execution fabric). It ships spec-aligned services plus practical internal stores for durability.
Why JARVIS exists
A standard only becomes credible when you can:
- Run it end-to-end.
- Observe real artifacts.
- Debug failures without guesswork.
- Compare alternative implementations against a working baseline.
JARVIS is that baseline.
What you get
End-to-end bounded execution
Composite runs decompose goals into NodeRuns, map subtasks via bounded candidate sets, and execute under enforceable constraints.
Durable evidence by default
Every run produces durable events and artifact references so behavior is replayable and auditable.
A reference for implementers
If you’re building your own ARP components, JARVIS is a practical baseline to compare behavior and contracts.
An incremental adoption path
Start by running the stack, then extend it with your own capabilities or swap in your own conformant services.
What’s inside the stack
ARP Standard v1 services (spec-aligned)
- Run Gateway
- Run Coordinator
- Atomic Executor
- Composite Executor
- Node Registry
- Selection Service
- PDP (optional)
JARVIS-only durability primitives (implementation choices)
- Run Store
- Artifact Store
- Event Stream
JARVIS is an implementation. The Standard is the contract. You can swap pieces as long as they remain conformant.
Repositories
Core JARVIS repositories for the reference implementation.
Run Coordinator
Run authority: state, enforcement checkpoints, dispatch, and durability hooks.
View repository →Node Registry
Catalog of NodeTypes (including built-in planners and first-party atomic packs).
View repository →Quickstart
Run the version-pinned stack locally (Docker Compose pulling GHCR images) and execute a composite run end-to-end.
# Run the pinned stack (JARVIS_Release)
git clone https://github.com/AgentRuntimeProtocol/JARVIS_Release
cd JARVIS_Release
cp compose/.env.example compose/.env.local
# Set STACK_PROFILE=dev-insecure in compose/.env.local for a no-token quickstart
docker compose --env-file compose/.env.local -f compose/docker-compose.yml pull
docker compose --env-file compose/.env.local -f compose/docker-compose.yml up -d
# Health check (Run Gateway)
curl -sS http://127.0.0.1:8081/v1/health How teams use JARVIS
Learn
Run it locally, inspect runs, and build intuition for bounded orchestration + durable artifacts.
Extend
Add new capabilities (atomic or composite) and validate behavior with repeatable evaluation.
Replace
Implement one component at a time and validate conformance against the Standard.