Architecture Decision Records
Status: Canonical index
Last updated: 2026-07-05
Purpose
ADRs record immutable architectural decisions — context, decision, consequences, and alternatives.
Template: STANDARDS/templates/adr-template.md
Index
Foundation (ZEP)
| ADR | Title | Status |
|---|---|---|
| ADR-001 | Why ZEP exists | Accepted |
| ADR-002 | Documentation first | Accepted |
| ADR-003 | Runtime contracts | Accepted |
| ADR-004 | Adapter architecture | Accepted |
| ADR-005 | Platform vs product separation | Accepted |
| ADR-006 | Enterprise architecture governance | Accepted |
AI & intelligence
| ADR | Title | Status |
|---|---|---|
| ADR-007 | Benchmark never changes runtime | Accepted |
| ADR-008 | Human approval mandatory | Accepted |
| ADR-009 | Why PL-003 exists | Accepted |
| ADR-010 | Why PL-004 owns learning | Accepted |
| ADR-011 | Products never own intelligence | Accepted |
| ADR-012 | Why version registry exists | Accepted |
| ADR-013 | Presentation belongs to products | Accepted |
Legacy location
Original ADR-001–006 authoring path: platform/adr/ — superseded by this directory for navigation.
Registry index: zaixos-registry ADR catalog
When to write an ADR
See ARCHITECTURE/decision-flow.md
Breadcrumbs: Home → ADR