Skip to content

DriftOps

BRYAN DAVID WHITE edited this page Feb 20, 2026 · 1 revision

DriftOps (Correction)

When reality diverges from what was recorded — detect it, log it, patch it.

Systems drift. Assumptions go stale, decisions become outdated, reality diverges from intent. DriftOps makes drift visible and routes it to the person who can fix it.

Source: coherence/drift/


Drift Signals

A drift signal records:

Field Purpose
Severity low / medium / critical
What Drifted What no longer matches the recorded state
Evidence How it was detected
Affected Which DLRs, assumptions, or canon entries are impacted
Proposed Patch What should be done to restore coherence
Patch PR Link to the fix (added after PR is opened)
Status open / patched / wont-fix

Drift Resolution Flow

stateDiagram-v2
    [*] --> Detected: assumption expired /<br/>decision invalidated /<br/>canon contradicted

    Detected --> Open: create DRIFT-NNNN.md<br/>assign severity

    state Open {
        [*] --> Triage
        Triage --> Low: minor
        Triage --> Medium: notable
        Triage --> Critical: blocking
    }

    Open --> PatchPR: open patch PR<br/>link in drift record
    PatchPR --> Patched: PR merged /<br/>status → patched
    Open --> WontFix: accepted risk /<br/>status → wont-fix

    Patched --> [*]
    WontFix --> [*]
Loading

Critical drift blocks releases until resolved.


Common Drift Sources

Source Example
Assumption expired ASM-0001 stated "vendor supports v2 API" — they deprecated it
Decision invalidated DLR-0003 chose library X — it's now unmaintained
Canon contradicted architecture.md says "no external deps" — a PR added one
External change Regulatory requirement changed

Creating a Drift Signal

  1. Go to coherence/drift/README.md in the repo
  2. Click the "Create New Drift Signal" link
  3. Fill in severity, evidence, affected records, proposed patch
  4. Commit to a branch and open a Patch PR

Rules

  • Every expired assumption should generate a drift signal
  • Critical drift blocks releases until patched
  • Drift records are never deleted — set to patched or wont-fix
  • Each drift signal should reference specific DLR/ASM/canon entries

See Also

  • IntelOps — assumptions that trigger drift when they expire
  • ReOps — DLR owners respond to drift signals
  • Coherence Score — open drifts reduce the score (5 pts each)

Clone this wiki locally