Operating Principles

1. FIG. P1 — Small kernel, readable tree. The kernel source tree is deliberately constrained. Every subsystem must justify its presence. The goal is a kernel an experienced operator can read and understand in a reasonable period. (diagram)
2. FIG. P2 — Conservative networking stack. Network protocols are implemented defensively. No experimental congestion algorithms, no hidden telemetry, no auto-negotiated cloud services. The network stack serves the operator, not the network. (diagram)
3. FIG. P3 — Local-first tooling philosophy. All system tools operate on the local machine by default. Remote operations require explicit operator intent. The system never assumes an internet connection. (diagram)
4. FIG. P4 — Source-visible system architecture. Every component of the base system ships with complete source code. The build process is documented, reproducible, and does not require binary bootstrap blobs. Operators are encouraged to read the source. (diagram)
5. FIG. P5 — No decorative complexity. Features are added only when they solve a demonstrated problem for system operators. Cosmetic enhancements, animation, transparency effects, and graphical boot splashes are not part of the base system. (diagram)
6. FIG. P6 — Operator owns the machine. 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. (diagram)

SYSTEM CONSTRAINT: These principles are not marketing. They are engineering constraints enforced by the build system and the project governance document (see src/SYS_CONSTRAINTS).