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