Replication privacy
Transport membership, project authorization and content classification are separate decisions. Local-only surreal-memory has a never-synced adapter; trusted/public domain labels are not permission to transmit arbitrary data. Keep raw memory, credentials, session material and private keys local.
Default connected control uses a same-user Unix socket. Explicit loopback TCP requires a private bearer-token file and does not enable the deprecated unsigned mutation route. The MCP bridge has no TCP fallback. Pairing secrets require private transfer, while KBD replica signing authority remains independently checked.
Optional DHT publication and iroh relay traffic are distinct configuration choices. Disabling DHT alone is not a no-network/no-relay guarantee. See peer settings and data scopes.
Ownership and evidence
These routes remain useful after relocation. The current recovered Companion
source (docs/installation.md, docs/control-api.md) has no public remote or
certified release yet. Source inspection is not installed or peer acceptance;
final source/artifact identities and publication links remain release-owned.
Use local KBD without the optional extension, and the service operations guide for pack/Companion ownership. The integration contract is a one-way seam. Relocation history is a decision record, not a Companion repository URL.