Jev decision pipeline: packed state, stacked questions, gated routing
Breaks down an agent pipeline where Jev System One runs parallel Choice/Score/Noul decisions, so the LLM writes, Jev decides and code acts, at $0.42 for 10,000 decisions.
WHOEVER LEAKED THIS JEV DECISION PIPELINE SHOULD BE WRITING THE RFC I thought routing an agent through five steps meant five prompts, five parsers, and five places something could silently drift. Apparently not. This pipeline's setup is much more interesting: → STATE packs the inbound case into typed cards indexed across 12 use cases (email, meetings, contracts, leads, trading), no raw text passes the first column → TYPED QUESTIONS stacks 7 asks against the same state (Choice folder, Noul worth_reply, Score urgency, Choice action, Score viral_fit, Score lead_quality, Choice next_worker), one shot, no retries → JEV SYSTEM ONE runs choice, score and noul heads in parallel with no generation at all, 256ms median, tokens out literally zero → GATE routes each answer at 0.85, below drops to quarantine or review, above forwards to the next worker (draft_short, book_call, type_destination), no silent escalation → CODE acts on the typed label deterministically (mail moved, calendar link sent, slack ping, review folder), flags 6 routes drifting from the baseline this run so you get: States packed. Questions stacked. Gates routed. Acts deterministic. the interesting part isn't adding more steps. it's giving every column one job the next column can't do for it. Instead of one model that writes, decides and acts in one freeform turn, you split the pipeline: LLM writes, JEV decides, code acts, with 10,000 decisions at $0.42 and gate 0.85 holding every route. Pack the state. Stack the questions. Act in code.
This post quotes another post: “Long read: how to build a Jev-powered agent stack”