Version 0.2.0 · August 2026
[Download PDF] [Markdown] [BibTeX] [DOI]
Frequently Asked Questions
What is the relationship between the project, the protocol, and the implementation?
The Sovereign OS Project is an independent research initiative founded by Robert Potter and published at sovereignos.foundation. The Context Inversion Protocol (CIP) is Potter's proposed edge-first implementation profile: authority stays at the local edge, and models are replaceable utilities behind a gate. Sovereign OS (SOS) is published as Control Plane 1.6.0, an MIT-licensed local custody plane for sources, evidence, and operator-accepted knowledge. SOS is not CIP. CIP would sit in front of a plane like SOS; that gate is not shipped. The .foundation domain does not specify legal form or nonprofit status.
What has been published?
Whitepaper 0.2.0 defines CIP as a proposed profile and reports SOS Control Plane 1.6.0 as a public MIT prototype. The control plane implements capture, ingest, debrief, and retrieve over ordinary local files. It is available at github.com/robertpotter-dev/sos-control-plane. It is not a completed CIP runtime, not an HCP implementation, and it does not expose MCP. Independent verification of behavior remains future work.
Is Sovereign OS a conventional operating system?
No. Sovereign OS names a local control plane for personal context custody. It is not a released desktop or mobile operating system, Linux distribution, installable consumer product, or replacement for Windows, macOS, or Linux. Version 1.6.0 is a command-line custody plane with conversational review, not an installable OS.
Is this project related to Palantir or similarly named products?
No. The Sovereign OS Project published here is unaffiliated with Palantir or other similarly named products. This project focuses on individual control of persistent human context through a local custody plane. CIP remains a proposed mediation layer, not a completed HCP-MCP stack.
How does Sovereign OS differ from edge AI initiatives by major hardware vendors?
Sovereign OS shares the architectural premise that personal context should be processed on the edge. Hardware-first vendors are economically incentivized to protect on-device data because their primary revenue is derived from hardware sales, allowing them to implement edge-centric AI within proprietary ecosystems. SOS 1.6.0 is published as inspectable, hardware-agnostic open source (MIT) rather than as a vendor-locked on-device AI stack. It does not presently run local inference.
Why not utilize centralized cloud models for personal AI?
Centralized models require the continuous extraction of high-fidelity personal context to third-party data centers. Organizations whose valuations depend on data aggregation and algorithmic advertising are structurally incentivized to maintain this extraction model. The published SOS plane keeps sources, evidence, and accepted knowledge as local files rather than a multi-tenant profile. CIP would add a policy boundary so replaceable models never mount that store; that gate is not shipped.
What are the hardware requirements for Sovereign OS?
The published control plane is a local Node.js command-line interface and conversational review workflow. It does not require on-device foundation models. A later CIP mediation layer that routes live model calls at the edge may need more capable local hardware, depending on workload; that is not a requirement of version 1.6.0.
How does Sovereign OS relate to HCP and MCP?
The Human Context Protocol (HCP) is a research program for user-controlled context sharing. The Model Context Protocol (MCP) is a tool-transport protocol. CIP is proposed as an implementation profile that would later use those families for scoped disclosure and gateway transport. SOS 1.6.0 does not implement HCP or MCP. HCP is not required for the custody plane to exist; it is the vocabulary the paper uses when the remaining problem is scoped sharing with AI systems.