I STOPPED LETTING CLAUDE OPUS 5.5 MAKE DECISIONS THE DAY I BUILT THIS JEV AGENT FOLDER I used to let Claude decide, write and act on every single step -> now Claude only writes. Jev makes the calls, code does the acting, and every step leaves a receipt 10,000 decisions cost me $0.42 everything inside the folder: • the input > AGENTS.md - when to call Jev and when to skip it > state/build_state - goal, workers, done, missing, constraint. evidence, never a summary • Jev decides (questions/) > route - which model tier gets the task > next_worker - which worker moves next > relevance - keep or drop every tool output > done - is the goal really met > risky - will this send, pay or delete something? • code acts (rules/) > hard_rules - stop after ten actions, never publish anything unapproved > thresholds.yaml - act only on confident answers. fraud needs 0.95 • Claude writes (workers/) > research - sources and notes > writer - drafts and briefings > the one place in the folder where text gets generated • the proof > receipts/decisions.jsonl - options offered, chosen id, re-check, fallback > evals/ - dozens of my own labelled traces, thresholds tuned on them • the guards (hooks/) > pre_tool_use - every command checked before it runs > stop - confirms "all done" before the agent is allowed to quit median 300 ms per decision. the expensive model never waits on a yes or no again the engineer who can show this bill to their team stops being the person who uses AI and becomes the one who decides how it runs an LLM writes, Jev decides, code acts

Oct 2, 2026 · 8:47 AM UTC

9
24
182
18,166
Sort replies: Relevant Recent Liked
Replying to @AnnatarXBT
o preço por decisão
111
Replying to @AnnatarXBT
Interesting shift - how about the trade - offs?
78
Replying to @AnnatarXBT
Separating the thinker from the doer is the only way it scales
135