examples/ha-blueprints/README.md
8 ready-to-import HA Blueprints covering the highest-leverage automations
RuView's HA-MIND semantic primitives unlock. Drop the YAML files into
<HA config>/blueprints/automation/ruvnet/ and import from the HA UI
(Settings → Automations & Scenes → Blueprints → Import Blueprint).
| # | Blueprint | Primary primitive | Use case |
|---|---|---|---|
| 1 | Notify on possible distress | possible_distress | Healthcare / AAL / single-occupant |
| 2 | Dim hallway when sleeping | someone_sleeping | Convenience / sleep hygiene |
| 3 | Wake routine on bed exit | bed_exit | Morning routine / smart home |
| 4 | Alert on elderly inactivity anomaly | elderly_inactivity_anomaly | AAL / aging-in-place |
| 5 | Meeting lights + presence mode | meeting_in_progress | Conference room / WFH |
| 6 | Bathroom fan while occupied | bathroom_occupied | Humidity / privacy-mode-safe |
| 7 | Escalate on fall-risk crossing | fall_risk_elevated | AAL / preventive intervention |
| 8 | Auto-arm security when room not active | room_active + no_movement | Self-arming security |
Each blueprint validates against the HA blueprint schema (https://www.home-assistant.io/docs/blueprint/schema/). To check locally without an HA install:
# Requires python3 + PyYAML
for f in examples/ha-blueprints/*.yaml; do
python -c "import yaml,sys; yaml.safe_load(open('$f'))" && echo "✓ $f" || echo "✗ $f"
done
Five of the eight blueprints work under --privacy-mode (no biometrics
exposed). The other three depend on inferred states that themselves
derive from biometrics, so they still publish, but the operator should
audit before deploying in regulated contexts.
| Blueprint | Privacy-mode safe? |
|---|---|
| 01 Notify on possible distress | ⚠️ derives from HR/motion — state still publishes |
| 02 Dim hallway when sleeping | ⚠️ derives from BR — state still publishes |
| 03 Wake routine on bed exit | ✅ |
| 04 Alert on elderly inactivity anomaly | ✅ |
| 05 Meeting lights | ✅ |
| 06 Bathroom fan while occupied | ✅ zone-derived only |
| 07 Escalate on fall-risk crossing | ⚠️ derives from motion-variance — state still publishes |
| 08 Auto-arm security | ✅ |
The "⚠️" markers are the inferred-state-vs-raw-value distinction from
ADR-115 §3.12.3:
the state (e.g. binary_sensor.someone_sleeping) crosses the wire
even in privacy mode because it's derived server-side, but it's no
longer accompanied by the raw biometric values.
docs/integrations/home-assistant.md — operator guidedocs/integrations/semantic-primitives-metrics.md — per-primitive F1