A canary of a new planner prompt set caused a spike in unsafe tool invocations. Automated gates paused expansion. What should the release design specify next for multi-environment multi-agent deployments?
Select an answer to reveal the explanation.
Short Explanation
When a canary's safety metrics tank, you don't push through; you roll back to the last known-good planner and orchestrator package, re-validate health and safety evals, then plan a fixed forward release. Expanding traffic, deleting backups, or disabling logs only multiplies harm, removes recovery options, or breaks compliance.
Full Explanation
Multi-environment release strategies require explicit rollback. The correct design restores the last known-good planner and orchestrator artifacts, then re-runs health and safety evaluations before any new attempt. Continuing canary expansion ignores active safety signals. Deleting prior prompt backups eliminates recovery options. Disabling logging obstructs audit and response. Version prompt sets and tool policies as immutable artifacts and treat them like binaries in the rollback unit.