Comment

Comment by avinashjetwani

That’s the hard problem, and I don’t pretend it’s solved. jevmem’s bet is a save/skip gate (Jev probabilities + fixed thresholds in config), not "log every turn." On a held-out set of 66 messages I wrote, save/skip was 98.5%; that is a single author-built run, and I have not measured long-run drift or whether injected lines actually improve answers. Trivial "used SELECT" lines should fail the content/importance gates; if they don’t in real use, that’s a bug I want labeled with `jevmem wrong` / `missed` so `fit` can retune. Happy to hear where deciduous draws that line too.

No comments yet

Be the first to share your thoughts.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton