Companion connected control
Sovereign Sync belongs to the separate optional Companion repository. Full and mini continue to own local skills, signed KBD and their distinct learning paths. Neither pack installs Companion or requires it for ordinary team work.
The recovered source implements a same-user Unix control host, connected stdio MCP tools, signed push receipts and optional P2P supervision. Choose one headless, windowed or standalone host for the selected socket. MCP connects to that host; it is not a second network node. Local authority starts before peers.
Read installation, control routes, MCP tools and push recovery.
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.