phoebus_os/docs/ROADMAP.md
2026-09-26 14:36:38 -07:00

7.3 KiB

Roadmap

Priority order is deliberate. Do not skip a higher item because a later one is more interesting. Status vocabulary: Done, Partial, Next, Later.

# Item Status Evidence / notes
1 Verify the Bash baseline Done (retired) tagged v0.1.0-bash-reference; retired with evidence in docs/BASH-MIGRATION.md
2 Build the Rust architecture Done installer-rs/ workspace, 5 crates
3 Port the deterministic core Done phoebus-core (config, plan, policy, validation, models)
4 Port the destructive backend Done phoebus-executor (storage, LUKS2, Btrfs, Portage, boot, users, services)
5 Rust VM boot parity Done Full encrypted UEFI install + boot, zero failed units, 10.7 s
6 Finish the desktop Partial Mango + DankMaterialShell is the canonical desktop; greetd login; the live ISO boots the branded welcome + graphical installer and was verified in a graphical VM; installed-desktop verification pending
7 Finish Flatpak Partial flatpak 1.18.1 installed, flathub configured; bounded typed flatpak_* actions added; fast defaults install Calibre/GIMP/Flatseal system-wide from Flathub in the target (unit-tested, fail-closed verification; VM launch/MIME/update checks not run)
8 Instrument source/binary policy Done measured compile times harvested from emerge.log (326 entries); resolved-effect previews added
9 Background update preparation Partial distfile fetch VM-verified; --buildpkgonly skipped while deps need merging (recorded Ready); activation explicit
10 Snapshots / rollback Done (normal sys undo); recovery-entry boot manual normal sys undo acceptance PASSED on a fresh disposable clone (serial-rollback-20260926T030237Z-912f6386 PASS=11 FAIL=0: DB changed then restored, root marker gone, /home survives, boot running); retention + free-space gate unit-tested; selecting the Phoebus Recovery (known-good snapshot) BLS entry offline with no network/model is a distinct manual acceptance gate (see docs/VM-BOOT-VERIFICATION.md), separate from sys undo
11 AI privilege and privacy architecture Partial typed actions + enforced privacy boundary + guided proposal review + OS-level sandbox (systemd-run hardening) + approval-bound resolved effects; live call/sandbox not VM-verified
12 sys operations Done history, enable/disable, inspect, install, prepare-updates VM-verified; target-root consistency, execution-boundary validation, truthful ask failure, full transaction outcomes, empty-vs-unestablished plans, start/stop/restart + flatpak/nix/snapshot commands, deterministic --legacy administration, audited --broker/--legacy gates, unified multi-source updates, quiet proactive assistance, shared service layer (phoebus_installer::service), and 23-case VM acceptance suite (sys-acceptance.sh 23/23 PASS)
13 Kernel optimization policy Later conservative fragments only; SAFE/OPTIMIZED/AGGRESSIVE selection exists
14 ISO / release pipeline Partial manifest/verify/assemble-plan tooling; release gates are executable (gates --execute runs each gate's real command and reports Passed/Failed/NotRun from evidence; publish refuses unless every gate passed); no CI runner has executed the VM/seat/model gates end to end
15 Recovery environment Later recovery BLS entry generated; snapshot-based recovery entry written at install; full recovery image not built
— Rust TUI Partial ratatui UI with plan/ERASE and AI provider selection; not yet the default on all paths
— Graphical installer (welcome + wizard) Partial Quickshell/QML over the typed --gui-bridge; live graphical VM verified, including a detached install+boot; live AI call pending (ADR 0010)
— AI-guided install optimization Partial DeepSeek/OpenAI/local providers, evidence-gated typed review, mandatory at install with --no-ai break-glass; fixture-verified, no live call
— Nix as a built-in second lane Partial pinned-release bootstrap; nix-daemon active and nix shell nixpkgs#hello VM-verified; on by default
— Hardware-aware software selection (all lanes) Partial shared policy + candidate resolution + choose_package/set_package_preference (unit-tested); Snap first-use/install/refresh/remove, AppImage and custom-ebuild journeys VM-verified; strict Snap confinement and changed-revision update remain (ADR 0006 revised)
— AI-first package administration Done unified CLI (sys install, please, ask) and desktop GUI (phoebus-assistant) backed by shared service::* planning, PreparedPlan digests with replay protection, Polkit elevation, QML provisioning, conversation continuity (conversation::*), Nix attribute verification, Portage binhost checks, and cross-source removal
— Git workflow + agent guide Done this docs/ set, .githooks/, scripts/

Immediate next steps

  1. Physical-seat desktop: run Mango + DarkMaterial on a real VT (or a seat-providing VM) and verify kitty, DMS spotlight, lock, idle, the polkit agent, logout and reboot interactively (docs/DEVELOPMENT.md).
  2. Mango + DankMaterialShell graphical verification: Mango is now the default (ADR 0009). Install the mango profile and boot the Mango live ISO in a graphical, seat-providing VM and run the gates in docs/VM-BOOT-VERIFICATION.md. Default promotion was an explicit owner decision; verification is still required to claim stability.
  3. Offline recovery-entry boot: select the Phoebus Recovery (known-good snapshot) BLS entry with no network and no model, verify the selected snapshot, boot, and basic deterministic sys operation — recorded separately from the passed normal sys undo acceptance (ADR 0007, docs/VM-BOOT-VERIFICATION.md).
  4. Binary strategy: keep the official signed binhost for packages whose USE matches and use Flatpak/Nix for other binaries; do not publish a private Gentoo binhost (ADR 0006). Verify with emerge -pv and record reuse.
  5. Lane follow-up in the disposable VM: the installed sys matrix, Snap first-use/install/refresh/remove, AppImage acquire/launch/remove, and custom-ebuild build now have VM evidence. Exercise an actual Snap revision change and strict AppArmor confinement when suitable fixtures are available (docs/SYS.md).
  6. Live AI provider call: exercise sys ask and the installer guided path with a real 0600 key file; the path is currently fixture-verified only, and the systemd-run sandbox is not yet VM-verified.

Later

  • Secure Boot / UKI as a separate opt-in milestone (not enabled by default): key ownership and enrollment, signed UKIs containing kernel, initrd and command line, signed normal/previous/recovery entries, atomic updates and rollback, plus OVMF positive and tamper tests. Ordinary BLS entries never imply Secure Boot protection. Blocked until stage3 trust, recovery, and update paths are reliable.
  • Full recovery environment (network, LUKS, Btrfs, Portage/kernel repair).
  • Automated biweekly ISO candidate build with tiered tests and atomic publish.
  • AI OS sandbox (systemd sandboxing / namespaces / bubblewrap / Landlock).
  • Local model support; richer provider onboarding.
  • Optimised kernel profiles with real hardware detection.
  • Risk-class update policy (CORE / PROVEN / EDGE) and update preflight.