ARP Concepts
In this section, we identify a set of core objects and durable artifacts. They help bridge the gap between COP, an engineering mindset, and ARP, a real protocol that's implementable (and indeed implemented as the JARVIS stack.)
Standard vs. implementation
This section explains the shared mental model, a.k.a. what the objects mean and why they exist. For normative schemas and endpoints, see ARP Standard.
Core Concepts
- Capabilities and Nodes: what a
NodeTypeis, howNodeRuns are created, and howRuns are structured. - Candidate Sets: how
Selectionreturns candidate sets, which are bounded action spaces for planners, and how that limits “what the system can do next”. - Policy Checkpoints: how authn/authz and other access policy checkpoints are enforced.
- Artifacts and Replay: why events and artifacts exist and how they support replay and evaluation.
Related sections
- COP mindset and lifecycle: why “capabilities” matter.
- JARVIS behavior and defaults
- Copy/paste recipes