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
- HA-Jev ObservedA Home Assistant custom integration exposing Jev evaluations as sensors and automation actions.
- 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, and Vercel exposes it through an evaluation-oriented API.
- MAGI System on Jev ObservedAn open-source three-sage voting experiment inspired by Neon Genesis Evangelion.