Case study · located work
Axon Work integration
The author states that Axon Work uses Jev-style model decisions with a skill/action harness.
ObservedAxon Work author
- Problem
- The author states that Axon Work uses Jev-style model decisions with a skill/action harness.
- Jev’s role
- Decision layer feeding an action-delivery harness.
- Architecture
- Model decision → skill chain → action harness.
- Why it matters
- A decision model can be invisible infrastructure beneath a workflow product.
Code boundary
Jev answers the bounded questions described above. Thresholds, retries, side effects, and anything that must be reproducible stay in the surrounding application code. The research record does not capture this project’s exact question set or threshold values; read the linked source before copying the architecture.
Sources
Limitations
- A located repository or demonstration does not establish production reliability or independent validation.
Reusable pattern and related records
- Probabilistic predicate + deterministic action PlausibleJev supplies fuzzy predicates while TypeScript, policies, and workflows execute constrained actions.
- Home Automation Intent Layer Authored HypothesisA Home Assistant layer turning state changes into typed comfort, safety, and automation decisions.
- 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.
- Decision quorum PlausibleMultiple typed judgments are aggregated through voting or confidence-aware stopping.