Opus + Jev decision flow: typed state packed from 12 feeds, routed to 6 lanes
A demo video shows Jev's typed Choice routing a packed state into six isolated lanes with an outcome check vetoing drift, at $0.42 total and 242ms p95 per decision.
WHOEVER LEAKED THIS OPUS + JEV DECISION FLOW DESERVES A SEAT ON THE BOARD I thought routing an agent's output to action meant parsing JSON and hoping the right function got the right arg. Apparently not. This flow's setup is much more interesting: → SOURCES ingests 12 live feeds in parallel, each one typed to its own shape, no mixing meetings with leads in the same input → STATE packs every source into a 1,004-token typed record, drops everything the schema doesn't claim, no raw dump into the prompt → CHOICE routes the state through JEV's typed questions and returns one of 6 outcomes with a probability, no free-form string anywhere → FLOW SPLIT dispatches each choice to its own lane (research 15.9%, write 17.5%, review 17.3%, escalate 15.1%, quarantine 19.0%), lanes never cross → OUTCOME CHECK verifies gate passed, spend under cap, no auto-post, flags 6 routes drifting above the ledger baseline this run so you get: Sources typed. States packed. Choices probabilistic. Lanes isolated. the interesting part isn't adding more automations. it's giving every route a lane the next action can't jump out of. Instead of streaming 10,000 decisions through a $8 model and hoping no bad JSON slips to the executor, you run them through JEV at $0.42 total, 242ms p95, and let OUTCOME CHECK veto anything that drifts. Pack the state. Route the choice. Verify the outcome.
This post quotes another post: “Long read: how to build a Jev-powered agent stack”