βͺ Lambda Rollback Wizard

Guided 5-step Lambda version rollback with smoke tests and T-JOSH governance gate.

1 Β· Current Version
2 Β· Target Version
3 Β· Smoke Tests
4 Β· CLI Command
5 Β· Verification
Step 1 β€” Current Lambda Version
⏳ Fetching live version from /beak/system/status…
Step 2 β€” Select Target Version

Choose the version to roll back to. Review the change summary before proceeding.

Step 3 β€” Smoke Test Checklist

Complete all 7 smoke tests before proceeding to alias update.

0 / 7 tests passed
Step 4 β€” CLI Command Generator

T-JOSH governance approval required before executing. Copy command only after approval is obtained.

β€” Select target version first β€”
⚠ Ensure you have obtained T-JOSH approval before running this command in production.
Step 5 β€” Verification

Re-check system/status to confirm alias now points to target version.

Press "Re-check System Status" to verify.
βœ… Rollback Complete Log this action in the governance log and notify the on-call team.
πŸ” T-JOSH Governance Gate

Lambda Alias Update Requires Approval

Before updating the production alias, you must have T-JOSH sign-off. This action is irreversible without another rollback cycle.

Required before execution: 1. Record the rollback reason and incident/request ID
2. Confirm smoke tests are all passing
3. Notify on-call team via ops-journal or shift briefing
4. Log the approval in governance log (sd_gov_actions)
5. Confirm T-JOSH access is active (not expired)