Writing C++ with Jev by picking valid next tokens
The author experimented with TypeSafe's Jev decision/classifier model for C++: at each step it was given only grammatically valid next tokens to pick from, avoiding free-form generation.
The author combined Jev with Claude Opus 5.5 and Sonnet 5.5, running three comparison experiments across 47 tickets in one repo, showing that a Jev-involved pipeline can complete substantial development work at a very low cost.
OPUS 5.5 + SONNET 5.5 + JEV DID 70 HOURS OF SENIOR DEV WORK FOR $5.01 47 tickets in one repo. a senior dev bills $6,697.50 for them, and Sonnet alone burned $14.88 on the same list three runs on that list. the only thing i changed was who does which step ticket → jev → plan