Canonical Host + Satellite Bodies

One Mind Across Every Machine · Shipped · workstation, home

One primary memory store; satellite machines proxy tool execution and local sensors. Shared context, distributed hardware.

The ‘One Mind, Many Bodies’ architecture. A Canonical Host (e.g., an always-on Mac Studio or home server) acts as the primary memory store, conversation history, and identity. Satellite bodies (laptop, Raspberry Pi, etc.) proxy their local sensors and tool execution capabilities to the host.

The federation middleware routes requests between host and satellites. Satellites register their local capabilities (scanners, hardware, microphones) with the host. The host’s agent can request tool execution on any paired satellite, and results return through the authenticated peer channel.

Limits and invariants

Memory is centralized on the Canonical Host — satellites do not maintain independent conversation history.

Where this lives

• halbert_core/halbert_core/federation/
• halbert_core/halbert_core/agents/peer_conversation_store.py