Brain and body may be separated over the same protocol, later

Context

“Any device” and “one platform” imply that a phone, a board or a server may be a body driven by a brain elsewhere, and that one Tacid may drive many. This must be possible by construction without being built now.

The three plans

• Grok: multi-host tools (this Tacid drives other Linux boxes over SSH); a cluster profile only if Phase 3 is boringly solid.
• Fable: remote agent nodes on SBCs.
• Codex: tacid remote SSH-first without a central relay; multi-machine orchestration and team policy files as long-term direction.

Decision

The protocol is transport-agnostic from day one (ADR-0005) and every remote peer is its own principal. Phase 7 adds SSH and WireGuard transports with mutual keys, headless node profiles with a workstation as remote builder, and one Tacid driving another. Team genomes and fleet profiles come after 1.0. No relay, no account, ever by default.

Consequences

• Nothing in the core may assume the client and the daemon share a machine.
• Fleet work does not start until the single body is boringly solid.

Alternatives rejected

• A hosted control plane: the cloud product the manifesto refuses.