Comment

Comment by Jmeg8r

Author here. The honest framing: the 37/40 vs 33/40 result is against my own deterministic router, not against Jev, which I never ran on these cases. The 40 held-out decisions are correlated (paired latency preferences per task). p95 went from 143 ms to 467 ms on a busy host with identical decisions, so the 300 ms timeout is doing real work. The part I'd defend most is the control boundary: deterministic eligibility filtering before the model sees anything, and a receipt that records but never authorizes. Happy to go into the MPS setup, the AutoModel loading mistake, or why the recovery-choice profile failed acceptance and stays off.
parent Jmeg8r 1 month ago

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