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 user ran 15,000 GitHub issues through Jev, which checked four criteria (reproduction steps, clear failure, bounded scope, whether reading code was needed), resulting in 360 issues passed to Claude Sonnet 5.5.
i put 15,000 GitHub issues through Jev + Claude Jev checked four things before Claude Sonnet 5.5 opened a repo: reproduction steps, a clear failure, a bounded scope and whether the fix required reading the code 15,000 issues → 60,000 checks → 360 for Sonnet 5.5 Sonnet 5.5