Provider Operations Acceptance Authorization + Bounded Steady-State Control Activation Foundation
This gate separates an operations-acceptance decision from the authorization that could transition provider control into managed steady state. Staging can rehearse only a HOLD-bound, dual-control, short-lived authorization and dry-run control activation. It cannot claim production acceptance, active production control, live requests, or provider network activity.
SCHEMA
Operations-control schema
READYExpect schema 55 after migration 0055.
SEGMENTED SELF-TEST
Cloudflare-safe operations-control matrix
READYEach case runs in its own Worker invocation.
SAFE QA FLOW
Rehearse control authorization without accepting production operations
READYSafe QA must remain source HOLD / accepted NO, qa-rehearsal authorization, dry-run control activation, live requests 0, network NO.
AUTHORIZATION ATTACK PATHS
Operations-control authorizations that must fail closed
CONTROL-ACTIVATION ATTACK PATHS
Control activation 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
Operations-control production gates — do not fake these green
Leave these open until a real production operations-acceptance decision has been independently approved and an intentional production control activation has been executed. Staging cannot satisfy them.