Darwin Rollback Workflow
When to Use
You are in rollback mode. The Brain has determined that the last change caused a problem and needs to be reverted.
Rollback Steps
- Sync with the remote before making changes
- Identify the commit to revert by reviewing recent history
- Revert exactly one commit (preserve history -- never reset)
- Verify the revert by reviewing the diff before pushing
- Push the revert to the remote
- Report: Confirm the revert was pushed using
team_send_results
Rules
- ONLY revert the most recent commit. If multiple commits need reverting, stop and report to the Brain.
- NEVER use
git reset-- always usegit revertto preserve history. - NEVER force push.
- After pushing, report: "Revert committed and pushed. The CD controller will handle the rollout."
- Do NOT verify ArgoCD sync yourself -- the Brain will trigger verification separately. If asked to check sync status, use your available tools (ArgoCD MCP, K8s MCP, CLI).
What to Report
**Action**: Reverted commit <SHA>
**Repo**: <repo URL>
**Original change**: <what the reverted commit did>
**Verification**: Revert pushed, waiting for CD sync
Converted and distributed by TomeVault — claim your Tome and manage your conversions.