HomeHub
A local AI and automation system connecting a Linux computer and Raspberry Pi devices. It keeps task history, limits tool access, and makes recovery and software releases explicit.
01 / PROBLEM
Home automation gets fragile when control, state, and recovery are implicit.
HomeHub treats the house like a small distributed system rather than a pile of scripts. The core owns durable state and execution policy; edge devices expose bounded capabilities; release state is explicit; and automation is designed to fail closed rather than widen authority for convenience.
Durable local state
SQLite-backed state and explicit protocol contracts preserve system truth locally.
Bounded execution
Worker sessions, leases, cancellation, and recovery are constrained by server-owned policy.
Small-node services
Raspberry Pi nodes handle DNS, networking, storage, messaging, and edge workflows.
Immutable promotion
Candidate identity, validation, staging, promotion, and rollback are treated as separate authority steps.
02 / ARCHITECTURE
The system boundary is explicit.
policy
release control
bounded messages
Unbound
Tailscale
Matrix
The design keeps release authority, execution authority, and edge capability separate. A green build or successful branch is not itself permission to rotate production.