Official · E2 · artifact verified
Route smart-home assistant requests
TypeSafe's smart-home demo evaluates a request against many typed questions in parallel, then lets code use only the answers relevant to that request.
01 · Role in the system
What Jev does here
Jev classifies the request category, target domain, device type, and requested device action in one speculative batch. It also checks whether the request contains multiple actions. Code ignores irrelevant speculative answers, splits compound requests through a separate language model, and sends conversational requests to that model instead of treating Jev as a text generator.
02 · Control boundary
Where Jev sits
One request becomes parallel Choice and Noul judgments; deterministic code selects the applicable branch and owns device actions.
Code owns the loop, permissions, thresholds, validation, and side effects. Jev owns only the bounded judgments described above.
03 · Known limits
What this evidence does not prove
- The official page describes the demo architecture but says the full source repository will be available at release.
- The page publishes no accuracy, latency, device-coverage, or production-reliability benchmark for this assistant.
04 · Attribution
Public sources
This is an Official record: the example was published by TypeSafe itself.
- TypeSafe ↗Official · demo · public · checked 2026-09-18