§5. Scope and non-goals

planarian @ a924e09 · Spec v4.6 · snapshot main · all versions

Phase A in scope: everything in the Phase A roadmap row, on NixOS 26.05 with systemd, D-Bus, udev; btrfs/ZFS optional; root via a dedicated systemd service.

Out of scope for A: the model service (B), the sandbox tier on the real change path (B; the Firecracker gym target runs non-gating in A), approval broker and console write paths beyond §16 (C), PlanarianOS profiles and the Relaxed, Guarded, and Sealed postures (C), snapshot restore (C), Rust evaluator or init (D), kernel work (E). Interfaces to them exist as traits with one implementation.

Not requirements in any phase of this spec: the directions in docs/future-work.md §3–§8b and §11 (remote principals and the endpoint catalog, app capabilities, fleet membership and attestation, resource governance beyond model residency, forecasting, Asterinas convergence, self-improvement). The schema hooks in §9 and §10 exist so these can be added later without reopening the proven crates.

Bypasses. Every known route around a guarantee, open or accepted by design, is a row in docs/bypasses.md (§17b) with what it breaks, its mitigation, and the phase that narrows it. A guarantee in this spec holds only as widely as its row in that file allows.