Architecture pattern
Decision sidecar
A typed judgment service sits beside ordinary code; code owns effects and safety boundaries.
Plausible
What the pattern does
A typed judgment service sits beside ordinary code; code owns effects and safety boundaries.
Caveat
The extra network hop must beat a local rule or classifier.
Patterns are recurring shapes observed across the collected material. A repeated shape is evidence that developers converge on it, not evidence that it performs well in production.
Sources
Limitations
- The extra network hop must beat a local rule or classifier.
Where this pattern appears
- SemIf (formerly OpenJev) ObservedAn independent open-weights reproduction of Jev's runtime-defined typed-decision interface, running a locally hosted 4B model (e.g. Qwen3.5-4B) on a consumer GPU with a browser WebGPU demo, committed benchmark runs, and row-level output data.
- Local Activity Auto-Timeline Authored HypothesisA private desktop timeline deciding whether each app/window event starts, continues, or ends an activity.
- The strongest near-term architecture is Jev as a complement and control layer around generative models. PlausibleJev produces decisions rather than prose; Vercel and OpenRouter expose it through evaluation-oriented endpoints, and LangChain documents it as a routing and guardrail layer inside its own harness.
- TypeSafe Agent Skills ObservedTypeSafe's own published Claude Code plugin and skills.sh package that teaches coding agents to design and wire up Jev workflows.