36 lines
1.1 KiB
Markdown
36 lines
1.1 KiB
Markdown
# SillyHome Future v2 Architecture
|
|
|
|
## Core Principle
|
|
|
|
v2 is event-first. Home Assistant state changes enter the Event Core, which
|
|
updates runtime state, routes affected actuators, computes a decision, applies
|
|
safety and handoff gates, then writes an audit event.
|
|
|
|
## Store Split
|
|
|
|
- `runtime.json`: current states, audit trail and connection health
|
|
- `learning.json`: patterns, room profiles and scene profiles
|
|
- `control.json`: safety stage, handoff mode and paused automations
|
|
|
|
## Control Path
|
|
|
|
LLMs are not part of the control path. Local deterministic insights may explain
|
|
state, but switching decisions must remain inspectable and testable.
|
|
|
|
## v2 Milestones
|
|
|
|
1. Event Core and routing index
|
|
2. Store migration and backup/restore
|
|
3. Decision Engine v2
|
|
4. Handoff Matrix
|
|
5. Rooms and scenes
|
|
6. Dashboard v2
|
|
7. Add-on hardening
|
|
|
|
## Add-on Contract
|
|
|
|
The Home Assistant add-on is owned by this repository and does not copy code
|
|
from `sillyhome-next`. It starts the v2 API with `SILLYHOME_FUTURE_STORE`
|
|
pointing at `/data/future_store`, so runtime, learning and control stores are
|
|
kept inside the add-on data volume.
|