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