Rollback Brief

Know The Way Back Before You Move Forward

Scrub backward through the reverse recovery sequence — Flag Off → Service withdraw → Config restore → DB compatibility → Traffic revert — and see what recovers cleanly vs what is irreversible.

Code rollback does not equal complete recovery

Reverting a deploy may not undo migrations, flag states, or webhook payload changes. PromoJade maps reversible vs irreversible steps in every rollback brief.

Step 1Feature Flag OFFDisable custom-roles · mid-cycle-billing

Step 2Withdraw new service versionPull 204-rc1 from canary pods

Step 3Restore configurationRevert API_V2 / FEATURE_CUSTOM_ROLES env

Step 4Enable DB compatibility layerKeep custom_role_id readable; no drop

Step 5Revert traffic to old versionShift 100% to build 203

Generate Rollback Brief — compile from manifest + ladder
Scrub Backward — replay promotion in reverse
Inspect Irreversible Change — see data and config that cannot revert
Assign Rollback Owner — route recovery responsibility
Approve Recovery Plan — sign off before promotion window

Green Builds Still Need Context

Promote every build with the context production actually needs.

PromoJade is the Software Release Context Layer between source control, CI/CD, and production — not another pipeline. Know what moves, where it lands, and whether environments agree before traffic arrives.

Inspect A Release Book A Demo