Long-lived meaning
- canonical facts, dimensions, identity, and lineage
- planning assumptions and saved scenarios
- policy registry, approval queue, and proposals
- cross-domain publications and semantic retrieval
- auditable action intent and outcome
Household data becomes household operating context
From evidence to an approved action.
Homelab Analytics joins finance, utilities, assets, contracts, and infrastructure into canonical household semantics—then publishes views, scenarios, policies, and narrow agent tools without confusing an observation with permission to act.
Follow the data
Choose a domain. The same structural pipeline produces different facts, while capability packs own their semantic rules and operating views.
Close the operating loop
Analytics is only the first half. Explore the path from a published fact through simulation, policy, approval, actuation, and measured feedback.
Keep the boundary useful
Home Assistant stays the excellent device-facing system it already is. The platform supplies the cross-domain memory and reasoning that entity state should not be bullied into providing.
API · MQTT · WebSocket
Immediate reality
- devices, entity state, and event capture
- family-facing dashboards and voice surfaces
- local automation timing and edge resilience
- synthetic entities published by the platform
- execution of explicitly approved actions
Trust is product behavior
The platform is useful only if an operator can tell what a number means, where it came from, and whether the system is allowed to do anything about it.
Content-addressed landing, source metadata, observations, and reconciled projections preserve the route from payload to fact.
Sources, runs, publications, and scenarios expose age and remediation rather than quietly serving historical confidence.
Policies and agents may create explainable proposals. Approval remains the deliberate crossing into action.