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