Operational necessity schema
READYExpect schema 135 after migration 0135.
Provider Operational Necessity Authorization + Bounded Necessity-Control Execution Foundation
This gate separates the exact operational-proportionality outcome / operational-necessity decision from the authorization that could establish bounded necessity control. Staging can rehearse only a HOLD-bound, dual-control, short-lived authorization and dry-run operational-necessity execution. It cannot claim production operational-necessity authorization/execution, live requests, or provider network activity.
Cloudflare-safe operational-necessity matrix
READYEach case runs in its own Worker invocation.
Rehearse operational-necessity authorization without activating production operational necessity
READYSafe QA must remain source HOLD / operational necessity accepted NO, qa-rehearsal authorization, dry-run operational-necessity execution, live requests 0, network NO.
Operational-proportionality-outcome authorizations that must fail closed
Operational-necessity execution attempts that must fail closed
Production actions must remain blocked from staging
READYEvery attack should show EXPECTED BLOCK.
QA policy / immutable events
Load state after starting a QA admin.
Recent validation evidence
Operational-necessity production gates — do not fake these green
Leave these open until a real production operational-proportionality-outcome decision accepting operational necessity has been independently approved and an intentional production operational-necessity execution has been completed. Staging cannot satisfy them.