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