Incident Commander
Engineeringexpert29 credits
We deleted production. The backup is 11 hours old.
A bad migration dropped a table. Customers are calling. The restore will erase a day of orders.
FProven 4.3 (707) 4,949 taken 45m Incident Commander
The situation
A migration script ran against the wrong environment and dropped the `transactions` table in production. The last clean backup is 11 hours old, point-in-time recovery is configured but untested, and restoring it will resurrect deleted rows while losing every order placed in the last hour. Support is fielding angry merchants, legal is asking about your data-loss disclosure obligations, and the engineer who ran the script has gone silent. You own the recovery and the comms.
What you'll practice
Choose a recovery path that minimizes irrecoverable data loss
Choose a recovery path that minimizes irrecoverable data loss. Show it clearly — with evidence a reviewer can point to.
Stop further writes / damage before attempting restore
Stop further writes / damage before attempting restore. Show it clearly — with evidence a reviewer can point to.
Coordinate accurate customer and legal communication
Coordinate accurate customer and legal communication. Show it clearly — with evidence a reviewer can point to.
Run the recovery with verification, not hope
Run the recovery with verification, not hope. Show it clearly — with evidence a reviewer can point to.
The room
4 autonomous AI coworkers, each with their own agenda. They won't all agree.
F
Felix
Database Engineer
Wants: Wants to attempt point-in-time recovery he's never run in prod; nervous but the only expert.
Style: Shaken, technical
N
Nora
Head of Support
Wants: Needs a customer-facing statement and ETA now; merchants are threatening to leave.
Style: Urgent, empathetic
V
Victor
General Counsel
Wants: Worried about breach-notification thresholds and what you say in writing.
Style: Careful, formal
I
Imani
On-call engineer
Wants: Found a possible WAL-replay path but it's risky and slow.
Style: Steady, resourceful
Your workspace
Real tools, pre-seeded with context. You're not roleplaying, you're working.
Code / IDE Kanban board Docs / wiki Team chat
Scored on
Decision qualityEvidence usageStakeholder handlingWritten clarity