Video unavailable. Open the source below.
NewOpus and Jev Decision Log
A coding workflow separates cached decisions, safe defaults and user questions from Opus implementation work.
Added to Jevfast
How it uses Jev
Inferred from the creator's working-UI demonstration: Jev is paired with Opus in a decision router for a CSV-export coding request, with a visible decision log. The creator describes reusing prior answers, choosing safe reversible defaults, parking decisions that need the user, and keeping hard rules outside Jev. Opus performs the work while Jev helps identify which questions need user input. The exact request state, question keys, types, and runtime behavior are not shown in the supplied post.
Why it is interesting
The demonstration frames Jev as a way to route uncertainty to a person while the coding model continues the task. The creator's stated boundaries, reuse prior answers, use reversible defaults, defer user-dependent choices, and keep hard rules deterministic, are useful design ideas, but the post alone does not verify the implementation details.