Material product, safety, data, or integration decisions are recorded here. Accepted records are not rewritten to change their conclusion; a later record may supersede one while preserving its provenance.
| ADR | Status | Decision |
|---|---|---|
| 0001 | accepted | Keep the initial control plane local and dry-run only |
| 0002 | proposed | Gate any future Krish integration behind versioning, reconciliation, approvals, and human-only merge |
| 0003 | accepted | Isolate child branches and supersede accepted plans only through explicit promotion |
| 0004 | accepted | Export structural lineage through scoped references without raw-source fields |
| 0005 | accepted | Bind continuity validation to an atomic stream-local append revision |
| 0006 | accepted | Default to session-only raw data, exact archived scope, reversible deletion planning, and single-project reasoning |
| 0007 | accepted | Keep v2 private content in a process-local session vault while immutable events retain strict structural lineage |
| 0008 | accepted | Bind the exact current accepted plan version and scoped graph to a draft-only decision packet |
| 0009 | accepted | Inventory exact private-bearing legacy events and require a stale-safe non-executable plan before mutation |
Each ADR states its status, context, decision, consequences, verification, and
supersession relationship where applicable. Permission-expanding decisions need
explicit human approval before their status can become accepted.