Triage a busy inbox with Jev

The system is a pipeline: code pre-checks each email against its matter record, one Jev request asks six questions about it, and a deterministic router turns the answers into one of nine routes. Only a calm status request from the client on file goes on to a claude -p draft, and a Jev guardrail has to pass that draft before it reaches the send queue. The decision that matters most is that every threshold is worked out from a cost written down before any evaluation (THRESHOLDS.md), so the router is a pure function of Jev's probabilities, the pre-checks and a cost table, and every tie goes to a human. Read this after you've tried each milestone yourself, and compare the report in the last step with yours: it shows how to write up a small evaluation without overclaiming.