Skip to content

Concepts

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

Concepts

CoherenceOps implements four modules that form a continuous loop.

The Four Modules

graph LR
    subgraph IntelOps["IntelOps (Truth)"]
        CLM[Claims] --> PRV[Provenance]
        ASM[Assumptions<br/>+ half-life]
    end

    subgraph ReOps["ReOps (Reasoning)"]
        DLR[Decision<br/>Ledger Records]
    end

    subgraph FranOps["FranOps (Memory)"]
        CAN[Canon]
        CHL[Changelog]
    end

    subgraph DriftOps["DriftOps (Correction)"]
        DRF[Drift Signals]
        PAT[Patch PRs]
    end

    ASM -->|"depends on"| DLR
    CLM -->|"supports"| DLR
    DLR -->|"may change"| CAN
    CAN -->|"changelog"| CHL
    ASM -.->|"expires"| DRF
    DLR -.->|"invalidated"| DRF
    CAN -.->|"contradicted"| DRF
    DRF -->|"fix"| PAT
Loading

How They Connect

  1. IntelOps records what you believe (claims + assumptions)
  2. ReOps records what you decided based on those beliefs (DLRs)
  3. FranOps protects the commitments that result from decisions (canon)
  4. DriftOps detects when beliefs, decisions, or commitments no longer match reality

The loop: Believe → Decide → Commit → Drift → Patch → Repeat

Key Insight

Decisions depend on assumptions. Assumptions expire. When an assumption expires, the decision it supports may no longer be valid. DriftOps catches this and routes a patch to the decision owner.

This is why assumptions have half-lives and expiry dates — they're not permanent truths, they're time-bounded beliefs.

See Also

Clone this wiki locally