Architectural Decision Records (ADRs)
This directory documents all significant architectural and design decisions governing cordanaLLM/praetor. Each decision record captures the context, options considered, decisions taken, and lasting consequences for fleet engineering.
Decision Lattice Index
| ADR ID | Title | Status | Date |
|---|---|---|---|
| ADR-0001 | Universal Multi-Agent Context Transpiler | Superseded by ADR-0012 | 2026-09-01 |
| ADR-0002 | Highest-Standard-Wins Fleet Governance Lattice | Accepted | 2026-09-02 |
| ADR-0003 | Canonical Engine & Reverse-Dogfooding Topology | Superseded by ADR-0012 | 2026-09-03 |
| ADR-0004 | Ephemeral Worktree Gating & Ed25519 Exit-0 Receipts | Superseded by ADR-0012 | 2026-09-04 |
| ADR-0005 | Cloud-Native OCI Distroless Containerization | Superseded by ADR-0012 | 2026-09-05 |
| ADR-0006 | Hierarchical Multi-Tier Runner Matrix | Superseded by ADR-0012 | 2026-09-06 |
| ADR-0007 | Universal Frameworks Hub & Demand Deduplication | Superseded by ADR-0014 | 2026-09-07 |
| ADR-0008 | Spec-Driven Provider Integration | Superseded by ADR-0018 | 2026-09-12 |
| ADR-0009 | Structural Unification Before Further Fix Waves | Accepted | 2026-09-12 |
| ADR-0010 | Text Register per Audience and Task Class | Accepted | 2026-09-17 |
| ADR-0011 | One Hook Entrypoint, Plugin-First Client Wrapping, and a Governed Operational Rollout | Accepted | 2026-09-27 |
| ADR-0012 | Context Compilation, Gating, Delivery and Runner Routing as They Stand | Accepted; decision 4 Superseded by ADR-0013 | 2026-09-26 |
| ADR-0013 | Container Image and Helm Chart Delivery | Accepted | 2026-09-26 |
| ADR-0014 | Operator-Neutral Defaults: Deployment Data Becomes Operator Configuration | Accepted | 2026-09-27 |
| ADR-0015 | Interactive Documentation Figures from Vendored interfig | Accepted; amended by ADR-0016 | 2026-09-27 |
| ADR-0016 | Interactive Figures for Adopters Through a Managed Engine Family | Accepted; amended by ADR-0018; section 2 Superseded by ADR-0021 | 2026-09-27 |
| ADR-0017 | Generated Artefacts in Pull Requests | Accepted | 2026-10-01 |
| ADR-0018 | Forge Drivers Repaired in Place Instead of a Spec-Driven Provider Engine | Accepted | 2026-10-18 |
| ADR-0019 | Released Surfaces Verified from Shipped Artefacts | Accepted | 2026-10-21 |
| ADR-0020 | Forge App Installation Tokens | Proposed | 2026-10-21 |
| ADR-0021 | Figure Player Bundle as an Engine Release Asset | Accepted | 2026-10-18 |
Lifecycle & Governance
- Immutable Numbering: ADR identifiers are strictly monotonically increasing (
0001,0002, ...). - Deterministic Statuses: Records transition through
Draft$\rightarrow$Proposed$\rightarrow$Accepted$\rightarrow$Superseded. - Receipt Binding: Any PR modifying or proposing an ADR requires an Ed25519 Exit-0 receipt signed by
standardsctl gate. - Immutable once Accepted: an Accepted record's body is never edited. A decision that changed, or a claim that stopped being true, is corrected by a new record that supersedes it; the older record changes only its Status line, to
Superseded by ADR-NNNN(ADR-0012 supersedes ADR-0001, 0003, 0004, 0005 and 0006 this way). One exception (ADR-0014 ยง7): replacing an operator-private identifier (a repository, organisation, host, path or account) with a neutral placeholder does not change a decision and is allowed in an Accepted or Superseded body, provided each redaction is listed with its date in aRedactionsnote at the end of the record. The rule is also stated in.agents/skills/adr-scaffold/SKILL.md.