Inside a decide-write-execute agent: Jev scores, Opus 5.5 writes, harness runs tools
The author shares an internal view of 194 decisions over 30 days: Jev scores each chunk hide/brief/raw, Opus 5.5 sees only the label, and the harness runs tools, catching a bad decision in 12 minutes on average.
jev's brain only has 3 moving parts. if one of them ever guesses, i turn it off 30 days in - 194 decisions, mean time to catch a bad one: 12 minutes zero code between the three parts, each one only sees what the last one wrote, not why: → jev decides - scores every chunk hide/brief/raw before anything gets written → opus 5.5 writes - never sees jev's reasoning, only the label it passed → the harness executes - runs the tool, captures the result, 2.5s a step → latency tornado ranks every step against a naive agent - kv cache alone saves 37ms, conditional instructions save 2 → loss surface gets checked after every batch - nothing ships until the contour tightens → every stall gets logged - 5 this week, down from 12 three weeks ago week 1 the harness executed before jev finished scoring. burned a full tool call on a chunk that got thrown out 3 seconds later. remember that part most "ai team" screens you see are a chat window with 3 tabs open. this is the actual decide-write-execute split with its own latency budget, which is why theirs stalls under load and this one just logs the stall and moves on $0 extra infra, it's just fewer parts allowed to guess this is the internal view i use to watch jev think, not a product screen. full clip is in the video which of the 3 parts do u think breaks first when i push volume up?
This post quotes another post: x.com/cyrilxbt/status/2101515130798297448