UC-16 · Group D — Level 3 · Granted Operation · ⭐
Approved and executed are proven the same request
Change one byte after approval and execution refuses — proof that the action that runs is the action that was approved, the endpoint binding.
The approved payload and the submitted payload side by side, one byte apart, diff highlighted, both canonical hashes rendered in full — and execution blocked at the enforcement point, offline, with no callback.
Approved and executed are provably the same request: the enforcement point verifies signatures, TTL, use count, and the fidelity binding offline — and brokering is the Level 3 generalization of inspect-and-release, inheriting its reservation discipline.
A live grants/verify succeeds on the intact payload; a real submit-brokered-interaction with a mutated payload comes back BLOCKED with FidelityVerdict: VIOLATION and AberrantActionSource: FIDELITY_VIOLATION (this build's editable aberrance policy promotes fidelity violations straight to SUSPEND_REQUEST — review immediate either way); the BrokeredInteractionRecord captures the mediated exchange.
“Approved and executed are two different requests in every system you own. Here they are provably the same request.”