Proof-gated architecture

An agent proposes an action. Your rules decide before that action runs.

The Compliance Operator is the gate. It is a policy written so it stays consistent, and a maths-proved implementation of that policy. It fails closed. It leaves evidence you can check.

The verdict is deterministic: the same state and the same proposed action get the same allow or deny. The glossary names that property deterministic governance, and it is this gate, not a second framework.

An allow is the gate’s decision on one action. It becomes part of the trace. It is not, by itself, the assurance claim. The claim includes its limit: what was shown, given which assumptions, and what is still trusted.

Proof Fabric is the name for that gate and Anchor used together. It is depth, not a second mechanism.

Spec++ is the method for writing the policy so the gate can be proved. Terms are in the glossary.

The Compliance Operator Framework is the SMART: SCOTLAND feasibility project. It is not another name for this gate.