Wednesday, 9:15am. Yesterday you caught the dashboard lying, ripped the enterprise filter out of churn, and revoked the triage agent's auto-close authority. The agent is sitting in a corner with its claws clipped — which is safe, but it also means a human is now reading every overnight alert by hand, and that human is you, and the board deck is due tomorrow. You can't keep a person in the loop for all 200 nightly alerts forever. So today's job is the harder one: put the agent back on-call without re-arming the failure. That means two changes that sound small and are not. First, change its *posture* — from auto-close to suggest-and-confirm, so it can do the volume work while a human keeps the kill authority. Second, change how it *ranks* — from counting rows to estimating blast radius, so three enterprise cancellations finally outrank three hundred trial signups. By tonight the agent ships again — this time with guardrails you wrote, and tests that prove they hold.
You'll walk out able to
- Redesign an agent's posture from auto-close to suggest-and-confirm without losing its throughput
- Score incident severity by blast radius (revenue at risk) instead of raw row count
- Spot the three failure modes that turn a confirmation step into rubber-stamping
- Pick the right reasoning budget for a triage call so cost and latency stay sane at scale
- Write the guardrail tests that prove an agent can flag but never silently silence
Your first task
Suggest, confirm, or auto?
You're at a whiteboard with the on-call engineer who's been drowning since you clipped the agent's claws. She wants it back, but safe. 'Just give it back auto-close for the obvious junk,' she says, 'and let it page me for the scary stuff.' It sounds reasonable. Before you draw the box, you decide what authority this agent actually gets.
What you'll answer
What's the right default posture for the rebuilt triage agent — the one that gets you volume without re-arming yesterday's failure?
Free · no card · we save your progress
Save your progress & earn the certificate
You've seen the opening — keep going free. 6 tasks · auto-graded · finish in 75 min and the certificate is yours. Free forever · no card.
No password. To sign in on your phone, request an emailed code on the sign-in page.
Already started? Sign in with an emailed code instead.