Architecture pattern
Probabilistic predicate + deterministic action
Jev supplies fuzzy predicates while TypeScript, policies, and workflows execute constrained actions.
Plausible
What the pattern does
Jev supplies fuzzy predicates while TypeScript, policies, and workflows execute constrained actions.
Caveat
Incorrect predicates are still operational errors even when outputs are valid.
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
- Incorrect predicates are still operational errors even when outputs are valid.
Where this pattern appears
- Goblin HR ObservedA small inspectable demo that evaluates candidates for an impossible mission.
- Probabilistic Rules Engine Authored HypothesisAn open-source engine combining Jev judgments with auditable deterministic conditions.
- 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.
- Axon Work integration ObservedThe author states that Axon Work uses Jev-style model decisions with a skill/action harness.