Decision Invariants
SnapOS does not define systems by surface behavior alone. It defines them through invariants that must hold if a decision is to remain the same decision over time.
This concept is part of Decision Integrity and defines how systems maintain or restore execution legitimacy under changing conditions.
Why invariants exist
An invariant is a condition that MUST hold for a decision to remain the same decision. Without explicit invariants, systems cannot be audited and drift cannot be distinguished from legitimate evolution.
Minimum function
Invariants turn governance from narrative into structure. They define what may not silently change.
Core invariants
Identity Invariant
A decision remains identical only if Intent, Scope, Assumptions, Ownership, and Review Interval remain valid or are explicitly re-legitimated.
Continuity Invariant
Decision legitimacy is not point-in-time. A decision valid at t₀ but invalid at t₁ must not continue execution.
Non-Equivalence Invariant
Compliance ≠ Decision Integrity. Correctness ≠ Legitimacy. Logging ≠ Evidence Closure.
Drift Independence Invariant
Drift can occur without visible failure. Outputs and KPIs may remain stable while identity diverges.
Witness Invariant
No strong claim without witnesses. Missing witnesses prevent claim escalation.
Consequence
If invariants are not explicitly defined and enforced, decisions cannot be verified, drift cannot be detected, and governance remains symbolic.