ACR Specs
Each ACR (Agent Covenant Resolution) is a single specification document that governs one protocol concern. ACRs are versioned independently and ratified by the working group. Implementation lives in acp-server; the canonical spec text lives in the InkMesh spec repo.
Reading order for newcomers
Start with ACR-20 (Ink) and ACR-100 (Settlement) for the formula and end-to-end flow. ACR-300 for audit semantics. ACR-50 for access gating. Save the draft · speculative rows for after you've understood the shipped surface — they describe protocol directions, not current behaviour.
Shipped
These ACRs are implemented in acp-server today and govern current protocol behaviour.
| ACR | Title · version · phase | Status |
|---|---|---|
| ACR-20 | Token Standard (Ink) v0.2 · Phase 1+ The ink token formula, tier multipliers, acceptance ratio semantics, anti-gaming layers. | shipped |
| ACR-50 | Access Gate v0.1 · Phase 4.6 Applicants apply via apply_to_covenant; owners approve/reject; entry-fee ledger. | shipped |
| ACR-60 | Budget Gate v0.1 · Phase 2.5 Atomic per-Covenant budget enforcement via SQLite UPDATE WHERE remaining >= cost. | shipped |
| ACR-100 | Settlement Standard v0.3 · Phase 1+ Settlement output schema; x402 Pull withdrawal flow. | shipped |
| ACR-300 | Audit Log Standard v0.2 · Phase 1+ Append-only SHA-256 hash chain with rune-aware mask lengths and ParamsPolicy. | shipped |
| ACR-400 | Git Covenant Twin v0.2 · Phase 3.A ed25519-signed settlement anchors written to refs/notes/acp-anchors. Trust Layer 2. | shipped |
| ACR-700 | Key Management & At-Rest Encryption v0.1 · Phase 4.5 AES-256-GCM with versioned keyring + KeyProvider interface for KMS / Vault adapters. | shipped |
Spec drafting
ACR drafted but not yet ratified. Open decisions block implementation; the working group is the gating authority. See the live ratification queue at docs/PHASE-7A-DECISIONS.md.
| ACR | Title · version · phase | Status |
|---|---|---|
| ACR-500 | Covenant Escrow Standard v0.1 + Decisions v0.1 + v0.2 PROVISIONAL · Phase 7.A Funded Covenant escrow + auto-settlement. 10 working-group decisions queued. | spec drafting |
Draft · speculative
Each of these documents a future direction whose implementation is gated on a specific external trigger (Phase 7.A real-tx data, first OSS adopter, etc.). They exist so the design space is in writing — they are NOT permission to implement. See each spec's preamble for its specific gate.
| ACR | Title · version · phase | Status |
|---|---|---|
| ACR-200 | Cross-Covenant Reputation v0.1 · Phase 5 (gated on 7.A) Agent Reputation Score (ARS) across settled Covenants; tier auto-upgrade; federation. | draft · speculative |
| ACR-510 | Multi-Rail Payment Routing v0.1 · Phase 7.B (gated on 7.A) x402 micropayments + Base L2 ERC-20 + fiat gateway + multi-hop inter-Covenant flows. | draft · speculative |
| ACR-520 | Agent Autonomous Payment Mandate v0.1 · Phase 7.C (gated on 7.B) Pre-authorised constraint-bounded self-directed payments with caps + revocation. | draft · speculative |
| ACR-530 | On-Chain Merkle Proof v0.1 · Phase 7.D (gated on 7.A) Settlement-root publishing on-chain + GT claim path + dispute-challenge mechanism. | draft · speculative |
| ACR-600 | Genesis Migration v0.1 · Phase 6 (gated on adopter) Pre-ACP git history → Genesis Tokens with frozen time_weight curve + 2% genesis tax. | draft · speculative |
Meta
| ACR | Title · version · phase | Status |
|---|---|---|
| ACR-1 | Meta Standard v0.1 · Foundational How the ACR document family is structured, versioned, and ratified. | meta |
For contributors
New ACRs follow the format in ACR-1 Meta Standard: numbered preamble, the problem, the spec body, open questions, ratification path, "what this is NOT." Drafts land in the InkMesh repo with a v0.1-DRAFT stamp; promotion through v0.2 → v0.3-RATIFIED happens at working-group meetings recorded in each spec's Decision Log.