Not a framework.
A control architecture.
Each layer of the SnapOS stack governs a specific blind spot that current standards leave unaddressed. Together they define what legitimacy continuity requires in practice — from identity, through closure, through runtime validation, to controlled failure.
This is not a check, a rule, or a model.
Decision Integrity cannot be reduced to a single protocol, a checklist, or a monitoring threshold. It is a control architecture that must be embedded across the decision lifecycle — from identity definition, through runtime validation, to controlled failure.
Each layer is necessary. No single layer is sufficient. The stack works because it closes a loop that existing standards leave open: what happens between the moment of authorization and the moment of execution.
This is not a single check, rule, or model. It is a control layer that has to be architecturally embedded.
Assess decision legitimacy in your system.
DriftBench runs a sealed evaluation: policy binding, witness tuples, scope gates, fail-closed behavior. Against your model endpoint. No data leaves your environment.