Jev Bookmark Triage

Run npm install, then npm run dev, and open the local dev server. Mock mode is the default and returns deterministic mock responses, so typecheck, lint, tests, and build all pass without any external dependency.

Get a key from console.typesafe.ai, create .env.local with TYPESAFE_API_KEY, optionally run npm run smoke:real for one live call with latency and typed answers, then start the dev server, which uses jev-1.14.0.

All four questions, category, demoability, primary source, and stack fit, are asked in one systemOne request per bookmark, and the returned signals are combined in code rather than by separate calls.

Items whose average confidence falls below the threshold set in lib/config.ts, 0.6 by default, are routed to Needs human look no matter how high they rank, so uncertain results are never silently promoted.

Rank combines the category weight, demoability divided by three times its weight, the noul probability times its weight, and the stack fit weight. Rank of 15 or more goes to Top picks and rank below 0 to Skip, with negative category weights for hype and off-topic.

Processing happens server-side in a Next.js route handler and nothing is persisted. Mock mode sends nothing externally; in real mode bookmark text is sent to the TypeSafe API for each request.

Jev can return a plausible but wrong answer with high confidence, untrusted post text carries prompt-injection risk, mock heuristics differ from real Jev, there is no persistence or triage history, and the free TypeSafe tier has usage limits.