This directory holds the Architecture Decision Records (ADRs) for the OpenDEA programme. ADRs capture the settled architectural decisions that emerge from the CR sequence (CR-1 onward). Each ADR is a short, immutable record of one decision: its context, the decision itself, its consequences, and the references that ground it.
Write an ADR when a decision is architecturally significant — meaning it constrains the design of OpenDEA going forward, it cannot be reversed cheaply, or it forecloses alternatives that downstream programmes depend on. Routine engineering choices do not need an ADR. An ADR is immutable once Accepted: do not rewrite it to retroactively match a new direction. If a decision changes, supersede the ADR by writing a new one that references the old and explains why it is being replaced; keep the original intact for the historical record.
| ADR | Title | Scope |
|---|---|---|
| ADR-001 | OpenDEA as semantic foundation | What OpenDEA is — and is not |
| ADR-002 | Core versus Profiles | Where new semantics live |
| ADR-003 | Canonical identity | How concepts are identified |
| ADR-004 | Knowledge graph abstraction | Vendor-independent GraphStore |
| ADR-005 | Provenance model | Observed / asserted / inferred / approved |
| ADR-006 | Temporal semantics | Five clocks; bitemporal; planned ≠ current |
| ADR-007 | Runtime/API separation | Viewer → Runtime → Specification layering |
| ADR-008 | Inference versus authoritative knowledge | No silent inference; explicit state transitions |
| ADR-009 | Agent authorization model | Read-only by default; PDP ALLOW/DENY/ESCALATE |
| ADR-010 | Scenario isolation from production state | Baseline + deltas; scenarios never mutate production |
| ADR-011 | Simulation adapter architecture | SimulationAdapter boundary; result provenance |
| ADR-012 | DMM / OpenDEA relationship | Diagnostic instrument vs semantic substrate; closed loop |
| ADR-013 | Core non-accumulation | Adapters absorb external complexity; the Core does not accumulate concepts |
| ADR-014 | Intelligence loop architecture | Five bounded layers (Observation → Signal → Pattern → Loop → ActionProposal); 8 binding rules for the composition layer that closes the CR-10 §P loop |
| ADR-015 | Capability classification by specialization | Abstract dea:Capability root; kinds as ADR-WSF-04 specializations in profiles; layer as attribute; ECF remains metadata; WSF federation mapping |
The ADRs in this index are Accepted as of their listed dates. They form the architectural baseline for OpenDEA. ADR-014 supersedes nothing; it records the composition-layer decisions for CR-012 (Enterprise Intelligence & Advanced Agentic Runtime), building on ADR-002 / 007 / 008 / 009.