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
Correct answer: C. When canary quality/safety tanks, roll back to last known-good packages and prompts, re-validate, then plan a fixed forward release. Expanding despite unsafe tools (A) multiplies harm. Deleting prior artifacts (B) removes your safety net. Disabling logs (D) is non-compliant. Rollback must be rehearsed and one command away for agent configs, not only for containers.
Full Explanation
Multi-environment release strategies require explicit rollback. Option C restores the last known-good planner/orchestrator artifacts and re-runs health and safety evaluations before any new attempt. Option A ignores active safety signals. Option B eliminates recovery options. Option D obstructs audit and response. Version prompt sets and tool policies as immutable artifacts; treat them like binaries in the rollback unit.