Home anticipator
Simulate a smart home that evaluates many possible needs at once, but changes nothing without approval.
- Time
- 60–90 min
- Level
- Speculative fan-out
- Shape
- Home state → parallel needs → one confirmable suggestion
- You’ll practice
- Fan-out · Contextual relevance · Human approval
The agent prompt
Copy this brief into your coding agent from the root of the project you want to build in. It names the behaviour, the constraints, and the checks to run — the decisions Jev makes stay explicit so you can see what the model actually decided.
Build a "Home anticipator" simulator in this repository using Jev from TypeSafe AI.
Inspect the repo and preserve its architecture. Use the official TypeSafe skill for current System One patterns, installing it with npx skills add typesafe-ai/skills --skill typesafe-ai if needed.
Create a fictional home-state editor for time, occupancy, temperature, open windows, light levels, and a calendar note. In one call, ask independent Noul questions about whether heating, cooling, lighting, ventilation, or a reminder would be useful, plus a Choice for the single most relevant suggestion. Display all answers, but use application code to surface only contextually valid suggestions. Every action is a simulation requiring explicit user confirmation.
Requirements:
- Use synthetic data only; do not integrate real devices or accounts.
- Keep TYPESAFE_API_KEY server-side.
- Use deterministic constraints so heating and cooling cannot both be proposed and unsafe temperatures always trigger human review.
- Explain speculative fan-out and why irrelevant answers are ignored.
- Add scenario presets, an event log, reset, and mocked tests for conflicts and low confidence.
- Document setup and what would be required for a real Home Assistant integration.
Run the relevant checks and summarize the decision-to-policy handoff.Built something like this
Community projects in the directory that solve a similar problem: