Running five agents on a hiring and firing policy with Jev triage
A business splits the chain from customer email to merged PR across five agents, with Jev scoring triage; two misses mean firing and retraining, at an average of $0.87 per ticket over 34 days.
jensen huang said every IT department will become the HR department for ai agents. i took that literally and gave jev a hiring and firing policy 34 days in - 5 agents on staff, 2 fired, 1 rehired, $0.87 average cost per closed ticket the whole business runs on one chain: customer email → gmail → jev → linear ticket → opus 5.5 → github branch → vercel preview → slack ping → me every agent has one job and one thing it's never allowed to touch: → support agent on haiku 4.5 - reads gmail, drafts replies, can't hit send → triage on jev - turns every email into a linear ticket, scores urgency 1-10, never writes code → builder on opus 5.5 - opens the branch, writes the fix, has zero access to main → reviewer on sonnet 5 - checks the diff against the ticket, rejects anything that drifts → billing agent - reads stripe, flags refunds, the refund button doesn't exist in its container two misses → logged → fired → replaced → retested on the same tickets. every agent goes through that loop, no exceptions for the expensive ones day 12 the support agent promised a customer a $1,400 refund in a draft. it couldn't issue it, but i almost hit send without reading. remember that part dario amodei said ai would soon write most of the code. nobody's talking about who writes the firing policy for it $0 extra infra - gmail, linear, github, vercel, stripe, slack, all tools i was already paying for the full chain is running live in the video, email coming in on the left, merged pr going out on the right which agent would u fire first?
This post quotes another post: x.com/beamnxw/status/2103335581115625571