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