Operator Owns the Machine
FIG. P6 — Operator sovereignty model. The operator (root) sits at the top with unrestricted authority. Three pillars support this authority: complete filesystem control (/), plain-text configuration (/etc), and manual pages as the authoritative system interface. Below — crossed out in red — are the rejected paradigms: hidden configuration, automated tools that obscure system state, and subscription-based service models. The machine serves the operator, not the other way around.
SOVEREIGNTY CONSTRAINT: The operator has root access, unrestricted file system control, and full authority over every installed component. The system does not hide configuration behind automated tools. Manual pages are the authoritative interface. No component of the system may refuse, override, or silently modify an operator's explicit instruction. See src/SOVEREIGNTY_CONSTRAINTS and THE MACHINE IS YOURS.