Publish a versioned runtime policy
Validate, simulate, review, and roll back runtime changes without weakening platform security floors.
Last updated 2026-08-07
What you'll achieve
- Review the effective policy before publication
- Detect conflicts with platform and plan limits
- Roll back through immutable history
Draft and validate
Open the project Runtime page and edit the versioned draft. Validate it to see the effective policy after platform security floors and plan entitlements are applied. A customer policy cannot weaken those floors.
Simulate and review
Run representative simulations and inspect the diff from the active version. Publish only the exact revision and lowercase SHA-256 document hash you reviewed. If the draft changed after review, resolve the conflict and repeat validation.
Confirm propagation
After publication, inspect edge acknowledgement and keep the prior version active as the recovery reference. Rollback creates a new immutable policy version; it does not erase history.
The advanced staged lifecycle is plan-governed. A failed publish must leave the previous effective policy in place.
Help improve this page
Sign in to send page-specific feedback. For account-specific help, email support@blinkhost.me.