Jev 管决策、Haiku 5 只管写代码
把决策全交给 Jev：31 个类型化问题 0.4 秒跑完、从 260 个文件里挑 4 个，Haiku 5 只写补丁，3 分 40 秒上线，成本 0.07 美元。
JEV + HAIKU 5 is outrunning my frontier stack... I took every decision away from the model. It only writes now. Hand it a task → Jev decides what it sees, where it goes, whether it runs → the model types. Full production ship in 3m 40s: → Jev scores the request before anything loads: answerable, in scope, not already done → 31 typed questions run in one call. 0.4s total → It picks the 4 files worth loading out of 260 → Haiku 5 writes the patch. That is its only job on this run → First patch failed the test. Jev caught it, re-scoped, second one passed → Jev holds the commit until the diff clears the permit rule 31 decisions. 2 model calls. 0 prompts rewritten. The bill: → Frontier stack, same task: $4.18 → This run: $0.07 → Not because the model is cheaper. Because it ran twice instead of nine times → A typed question costs less than the whitespace in your prompt Prompt engineering was people guessing what to say to the model. Jev engineering is deciding what the model never has to see. Not a router. A router picks a model. Jev picks whether there is anything to send. Jev decides, the model writes. Nobody needs a bigger model for the deciding part.
这条是引用着另一条写的：x.com/0xcodio/status/2104195432209387524