No. 01 · FIG A · Deterministic execution gate

Execution gate

Resolve identity, policy, and scope at one deterministic boundary. Execution remains mechanically unavailable until all three checks agree.

FIG A · Deterministic execution gateAwaiting evaluation
Request
An execution request advances through identity, policy, and scope checks. A conforming request crosses the authority boundary; a scope mismatch stops before execution.ObservedEXECUTION REQUESTDeterministic checksIdentityPolicyScopeExecution boundaryAuthorizedEXECUTEObservationAuthorizationExecution

Ready: the request is observed, but no authority has resolved and execution remains closed.

GATE / CONFORMING / READY

An observed execution request advances through three checks in order. Identity resolves against the request principal, policy decides whether the operation class is permitted, and scope compares the requested boundary with the authorization envelope. A conforming request lifts the bolt and crosses into execution. A scope mismatch stops at the third check and the gate stays closed.

The drawing separates model output from execution authority. Brass marks the governing boundary and the permitted path, never the entire apparatus. Nothing downstream, neither commit binding nor the hash chain, can occur while the gate is closed.