ADRs capture significant, hard-to-reverse decisions with their context and consequences. Adding a verb to the action vocabulary, taking on an OCM addon dependency, or relaxing a safe default is an ADR-level change.
Format: Status · Context · Decision · Consequences · Alternatives considered. Where a
decision rests on an external fact, that fact is web-verified and cited (see also
../../COMPETITIVE.md).
| ADR | Title | Status |
|---|---|---|
| 0001 | Adopt OCM as the substrate (vs. a bespoke tunnel/agent) | Proposed |
| 0002 | Stack & language (cluster-side Go; control-plane/API/UI) | Proposed |
| 0003 | Tenancy model & multi-tenant isolation | Proposed |
| 0004 | Typed-intent action model (closed vocabulary, no shell) | Proposed |
| 0005 | AI / MCP server surface & Ardur as the PDP | Proposed |
| 0006 | Credential & key custody | Proposed |
| 0007 | Local MCP transport, scope, and authentication | Accepted |
| 0008 | Deterministic local advisory brain and evidence contract | Accepted |
| 0009 | Reproducible and identity-bound release supply chain | Accepted |
| 0010 | Native local desktop shell | Accepted |
| 0011 | Exact-decimal USD boundary for OpenCost namespace cost facts | Accepted |
| 0012 | Coverage-aware workspace rollup for OpenCost cost facts | Accepted |
| 0013 | Privacy-minimized DCGM GPU utilization facts | Accepted |
| 0014 | Split connector wire compatibility from adapter provenance | Accepted |
Planning ADRs remain Proposed until their implementation lane accepts or rejects them. Implementation-specific ADRs may be Accepted when the corresponding shipped slice provides the validation evidence.