Jev Home Assistant Sentinel

It is a Home Assistant integration for AI-assisted decisions around physical devices. It sends a bounded case to a decision model, applies a deterministic policy check, and records state verification separately from the command result, keeping the model's output advisory rather than directly actuating devices.

Hosted Jev over TypeSafe or OpenRouter, Clef and Clef Flash on Cloudflare Workers AI, open-weight Laya running locally on the same machine, and any engine that answers the same /v1/systemone request shape via the local_model setting.

api_with_local_fallback and local_with_api_fallback chain a hosted and a local provider using the existing cooldown, trigger and breaker machinery, while api_only and local_only are single-provider routes where a failure is reported rather than rerouted.

The provider name in configuration stays laya, but local_model chooses which checkpoint or engine answers, defaulting to laya and also accepting engines published as laya-multilingual and laya-typed-decisions. The value is not validated against a list, so naming another engine is configuration, not code.

The policy check is deterministic and the state verification is recorded separately from the command result, so the AI's recommendation never silently becomes the record of what happened. The README frames this as making the evidence visible and keeping recommendations advisory.

The README presents it as a HACS custom integration for Home Assistant, with a CI workflow and a Python 3.10+ requirement. The digest's README truncates inside the provider table, so follow the repository's own installation instructions for the exact HACS steps.

A model that returns typed values, each carrying a probability, rather than prose. The README notes TypeSafe coined the category alongside Jev on 15 September 2026 and stresses that Jev is one member of the category, not the name of it, which is why the integration can also reach Clef and Laya.