ReOps

ReOps (Reasoning)

What was decided, why, and what was traded off.

ReOps is the reasoning surface. Every major decision gets a Decision Ledger Record (DLR) — a structured document that captures context, options, trade-offs, blast radius, and rollback. When someone asks "why did we build it this way?" the DLR is the answer.

Source: coherence/decisions/

---

Decision Ledger Records

A DLR has these sections:

Section	Purpose
Context	What problem are we solving? Why now?
Options Considered	What alternatives exist
Decision	What we chose and why
Trade-offs	What we gave up
Assumptions	Which ASM-IDs this depends on
Blast Radius	Scope of impact if wrong
Rollback	How to reverse it
Owner	Who is accountable post-merge

---

DLR Traceability

A DLR is the hub connecting assumptions, claims, canon, and drift:

graph TB
    DLR[DLR-NNNN<br/>Decision Record]
    DLR -->|"depends on"| ASM1[ASM-0001]
    DLR -->|"depends on"| ASM2[ASM-0002]
    DLR -->|"supported by"| CLM[CLM-0001]
    DLR -->|"may change"| CAN[canon/<br/>architecture.md]
    DLR -->|"owned by"| OWN["@owner"]
    ASM1 -.->|"expired →"| DRF[DRIFT-NNNN]
    DRF -->|"assigned to"| OWN
    DRF -->|"fixed by"| PAT[Patch PR]
    PAT -->|"updates"| DLR

    style DLR fill:#2c3e50,color:#fff
    style DRF fill:#c0392b,color:#fff
    style PAT fill:#27ae60,color:#fff

Loading

---

When to Create a DLR

A DLR is required for Major PRs:

• PR has the major label
• PR changes 10+ files
• PR touches coherence/canon/, coherence/intel/, or core architecture

Everything else is a normal PR — no DLR needed.

---

Creating a DLR

1. Go to coherence/decisions/README.md in the repo
2. Click the "Create New DLR" link
3. Fill in the template
4. Commit to your feature branch
5. Reference the DLR path in your PR description

---

See Also

• IntelOps — assumptions that DLRs depend on
• FranOps — canon that DLRs may change
• DriftOps — what happens when a DLR is invalidated
• Policy Gates — CI enforcement of DLR requirement