Claude + graph + Jev workflow splits bug fixing into plan, review, and evidence checks
Proposes splitting bug fixing so Claude plans and writes code, a graph structure separates building from review, and Jev verifies evidence before approval, leaving reusable checkpoints for repeat fixes.
this is certified f*cking gold CLAUDE + GRAPH + JEV MAKE YOUR NEXT FIX EARN ITS KEEP repeat fixes burn time and tokens the same mistake gets another invoice give the workflow a better split: > Claude plans the work and writes code > the graph separates building from review > JEV checks the evidence before approval keep the checks after the fix ships let the next run catch the comeback send this prompt to your coding agent before you build another workflow the best fix leaves a tripwire behind
This post quotes another post: x.com/hanakoxbt/status/2101709924828934222