phoebus_os/docs/ROADMAP.md
Phoebus 297f3201ff
Some checks are pending
ci / test (push) Waiting to run
feat(sys): hardware-aware lane selection and new lanes
Replace the fixed category routing (ADR 0006) with a shared, inspectable,
hardware- and preference-aware selection policy over resolved candidates from
Portage (source/binary/vendor), Nix, Flatpak, Snap, AppImage and the Phoebus
overlay. The policy keeps base components under Portage, separates hard
constraints from preferences, honours and persists explicit choices, errors
instead of silently switching lanes, and reuses an already-installed lane.

- phoebus-core::selection: the pure policy (16 tests: base-system, low-memory
  vs high-core, sandbox requirement, GPU/arch/storage rejection, explicit
  preference, unavailable backend, reproducibility, render).
- phoebus-executor::chooser: resolves real metadata and hardware facts.
- phoebus-executor::{snap,appimage,ebuild}: new lanes. Snap detects daemon and
  confinement and installs app-containers/snapd through Portage; AppImage
  adopts images with a pinned SHA-256, checks the ELF architecture without
  executing, integrates a desktop entry and preserves user data on removal; the
  custom ebuild overlay binds approval to the ebuild content digest and builds
  through Portage's sandbox.
- Typed actions choose_package / set_package_preference / snap_* / appimage_* /
  custom_ebuild_* with strict validators; the assistant prompt and schema are
  reconciled (no category routing; custom ebuilds are untrusted).
- Installed sys: the installer locates the trusted static binary, copies it to
  /usr/local/bin/sys and proves it runs in the target chroot before the
  recovery snapshot, failing closed if absent; the VM harness fetches sys.
- docs/SYS.md: command/action reference and acceptance matrix; ADR 0006 revised.

Host gates pass: fmt, clippy (no new warnings), workspace tests, make test,
release and static sys builds. VM lane journeys remain pending (see HANDOFF).
2026-09-23 18:35:26 -07:00

5.8 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 default (dwl fallback); 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; no app installed yet
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 Partial snapshot sets + history VM-verified on Btrfs; coordinated rollback, sys undo, recovery entry, retention and free-space gate implemented + unit-tested; destructive VM acceptance test pending
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 Partial 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, and start/stop/restart + flatpak/nix/snapshot commands added (unit/integration-tested; VM gate pending). Installed-target sys now provisioned by the installer (unit-tested; VM gate pending)
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, atomic publish and signing helpers added; no CI runner has executed a gate
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, AppImage and custom-ebuild backends implemented (unit-tested); VM journeys pending (ADR 0006 revised)
— Git workflow + agent guide Done this docs/ set, .githooks/, scripts/

Immediate next steps

  1. Physical-seat desktop: run phoebus-session/dwl on a real VT (or a seatd-backed session) and verify kitty, wofi, phoebus-menu, phoebus-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. Rollback VM acceptance: deliberately break an update in the disposable VM, run sys undo, reboot detached, verify package-state consistency, then boot the recovery entry with no network or model (ADR 0007).
  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 acceptance in the disposable VM: run the sys acceptance matrix (installer/tests/vm/sys-acceptance.sh) on a booted installed disk, then a Snap install/refresh/remove, an AppImage acquire/launch/remove, and one custom-ebuild build (docs/SYS.md). This is the remaining proof for the new lanes and the installed-sys lifecycle.
  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

  • 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.