Ground answers in a bounded world view.
Freshness, confidence, device state, presence, context, and recent transitions are projected for intelligence without handing an agent the underlying store.
Local household intelligence
HAVEN keeps intelligence close to the household and authority explicit.
HAVEN is a public, local-first assistant for a computer, personal information, and the connected world around it. Home Assistant and other device protocols are providers inside that world, not a separate product mode.
The boundary
A model response is never permission to mutate a device.
HAVEN keeps interpretation, evidence, authority, execution, consequence, and memory as separate steps. Household scope, role, justification, evidence freshness, risk, confirmation, and human override remain part of the decision path.
What is public
A household surface with a governed core.
The public repository exposes the contracts and local runtime seams. It does not make the Hub a household authority, provide a cloud fallback, or turn a demo fixture into live evidence.
Public repository license: Apache-2.0. Provider credentials, household data, and installation state remain with the operator.
Keep permission outside interpretation.
Rules and direct household actions use the same authority path. Safe-automatic, confirmation-required, forbidden, stale, fallback, and unavailable states remain distinct.
Use provider seams instead of vendor assumptions.
Home Assistant, Bluetooth, Wi-Fi discovery, speech, and model backends bind through explicit protocols. A discovered device or available model is not automatically trusted or activated.
Leave a reconstructable receipt.
Accepted and blocked transitions emit typed events. Actions connect request, interpretation, evidence, authority decision, command, response, and event identifiers without persisting confirmation material.
Two honest compositions
Try the boundary or connect a real household.
The repository has an explicit demo composition for trying the experience without network access, credentials, or real hardware. The production composition builds a real installation from persisted setup and reports unavailable evidence honestly when a provider or device is not connected.
Live Home Assistant, native audio, Bluetooth, local models, and durable history are installation capabilities. They are not silently implied by opening the demo surface or by a repository link.
Plugin marketplace · coming soon
A plugin will read exported receipts through the Hub. It never runs inside HAVEN.
The marketplace catalog is browsable today; the export and relay path that would move any data is not built yet. HAVEN's local providers (device, speech, and model integrations) are a separate concept from a plugin. Providers run inside HAVEN, under the same authority boundary as HAVEN's own fixtures. A plugin runs outside it entirely.
Read what a household chose to export.
HAVEN emits a versioned receipt export locally. Forwarding it to the Hub will be an explicit, opt-in, per-installation decision. A plugin will only ever read that export, relayed through the Hub's signed plugin catalog — never by connecting to a household's HAVEN instance directly.
Execute, propose a rule, or see raw evidence.
A plugin never receives household-identifying data, the underlying evidence store, or execution or rule-proposal authority. Those stay exclusively local and authority-gated, the same as every HAVEN provider.
TraceGlass (diagnostic: decision-chain reconstruction) integrates primarily as a local analyzer today — against HAVEN's public TraceAnalyzer contract — not through the Hub. It has a private implementation outside this repository; the household's full receipt chain never leaves the installation for its own analysis. It is listed in the Hub catalog as a preview of the capability vocabulary a future, narrower Hub-relayed variant would share; a third-party plugin satisfying the same catalog entry would hold no different access.
Support public research
Support the household boundary.
Donations help fund local-first household software, public interfaces, evaluation, and the governed research that keeps model capability separate from authority.