Kernel hardening
Monarch OS is intended to minimize the node appliance’s attack surface through immutable releases, restricted administration, measured changes, and a small runtime footprint. That is a design direction, not a claim that a particular hardened kernel is publicly released or independently verified.
Exact build settings, service layout, control-plane configuration, and Foundation deployment policy are not public operator instructions. Do not derive production security guarantees from historical configuration lists.
Before release, the security posture needs reproducible configuration, signed artifacts, an explicit threat model, independent review, vulnerability-response policy, supported hardware, and evidence that recovery remains possible without weakening authentication.
See Hardware sovereignty.