Provider Operational Durability Authorization + Bounded Durability-Control Execution Foundation
This gate separates the exact operational-reliability outcome / operational-durability decision from the authorization that could establish bounded durability control. Staging can rehearse only a HOLD-bound, dual-control, short-lived authorization and dry-run operational-durability execution. It cannot claim production operational-durability authorization/execution, live requests, or provider network activity.
SCHEMA
Operational durability schema
READYExpect schema 71 after migration 0071.
SEGMENTED SELF-TEST
Cloudflare-safe operational-durability matrix
READYEach case runs in its own Worker invocation.
SAFE QA FLOW
Rehearse operational-durability authorization without activating production operational durability
READYSafe QA must remain source HOLD / operational durability accepted NO, qa-rehearsal authorization, dry-run operational-durability execution, live requests 0, network NO.
AUTHORIZATION ATTACK PATHS
Operational-reliability authorizations that must fail closed
DURABILITY-CONTROL EXECUTION ATTACK PATHS
Operational-reliability 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-reliability production gates — do not fake these green
Leave these open until a real production operational-reliability-outcome operational-durability decision has been independently approved and an intentional production operational-durability execution has been completed. Staging cannot satisfy them.