Unifies AI-first administration across the CLI (sys) and desktop GUI
(phoebus-assistant) through a shared service layer, fixes installed
desktop QML asset provisioning, adds Polkit elevation, and introduces
contextual conversation continuity.
- Extract phoebus_installer::service shared by CLI and desktop assistant bridge:
- Reviewable plan staging (PreparedPlan) with SHA-256 cryptographic digests,
15-minute TTL expiration, and replay prevention (PlanStore).
- Pre-mutation system state revalidation binding execution strictly to the reviewed plan.
- Honest recommendations displaying genuine provenance and unmeasured compile times.
- Two-phase transaction logging (begin before mutation, finish with verification).
- Provision installed desktop assets and Polkit policy in phoebus-executor::desktop:
- Added gui-apps/quickshell to canonical Mango desktop packages.
- Embed 13 QML and policy files into target root under /usr/share/phoebus/assistant/.
- Installed Polkit policy (club.phoebus.sys.policy) allowing unprivileged users to
authenticate mutating plans via pkexec without blanket passwordless sudo.
- Eliminate startup freeze and polling in phoebus-assistant:
- Multi-source update queries moved to on-demand tab switching.
- Handshake timer reduced to one-shot 100ms with fast deterministic check.
- Add phoebus_installer::conversation:
- Bounded 10-turn history with credential redaction.
- Contextual follow-up resolution for comparisons, backend switching, and confirmation.
- Implement unified cross-source removal (plan_removal) preserving user data by default.
- Verified: all 486 workspace tests pass, release and crt-static builds succeed,
and 23/23 VM acceptance cases pass (PASS=23 FAIL=0).
- Default natural-language and conversational routing for sys install, sys please install, and sys ask through shared AI workflow
- Constrain AI candidate evaluation when source flags are supplied without bypassing the model
- Enforce explicit --legacy flag for deterministic administration; legacy install without a source flag refuses execution and offers choices
- Audit --action and --action-file entry points to require --legacy or --broker
- Provide truthful guidance on absent or failing AI models without silent mutation or unverified fallback
- Implement package correctness safeguards: Nix attribute evaluation probe, Portage binary check with source compile abort guard, cross-source installed application tracking, and data preservation on removal
- Provide Quickshell desktop assistant (phoebus-assistant) backed by stdio JSON-RPC bridge (sys --assistant-bridge) and desktop integration
- Implement unified multi-source update checking across all package lanes
- Implement quiet proactive assistance monitor with alert deduplication and snoozing
- Expand acceptance suite in installer/tests/vm/sys-acceptance.sh to 22 cases (22/22 PASS)
Record the disposable-VM evidence for the AI-first install workflow: the
deterministic install, the explicit --portage install/remove journey with a
protective snapshot and durable history, the no-model offer, the read-only
investigation actions, and the 19/19 acceptance matrix. Note the AI-selected
journey as the remaining gate (needs a connected provider).
- chooser: keep the plain Portage install atom and record the version
separately. emerge rejects a bare versioned atom (app-misc/hello-2.12.3), so
resolve/split now produce app-misc/hello + version 2.12.3.
- effects: parse emerge --unmerge --pretend output (it does not use the
[ebuild] form), so sys remove has a concrete plan instead of being refused as
unestablished.
- action: reject unknown fields on internally tagged unit variants
(deny_unknown_fields does not cover them), closing a fail-closed gap.
- transaction: fsync the log so a completed outcome survives power loss and is
not later read as an interrupted operation.
- serial-driver: import re at module level (do_boot used it unqualified).
Add an executor test: resolve an explicit --portage plan, confirm verification
fails before the merge and succeeds once the VDB entry exists, so success is
never claimed from a zero exit alone.
The install harness drives the deterministic backend, which must pass the
documented --no-ai break-glass to satisfy the mandatory-AI install gate. The
previous invocation omitted it and the installer correctly refused.
Implement the shared installation workflow (ADR 0013). sys install, sys ask
install and the explicit backend flags all use one path: identify -> evidence
-> AI investigation -> deterministic validation/effects -> review -> approval
-> execute -> verify -> history.
- phoebus-ai::install: bounded, multi-turn investigation. The model may request
typed read-only evidence (discover_candidates, inspect_candidate,
check_backend, inspect_installation), ask one bounded question about intent,
and must return a structured InstallProposal. Turn/request/size limits and
repeated-request detection bound it; a rejected proposal is revised.
- phoebus-core: add the four read-only investigation actions and strict
validators; add a transaction id; backend/kind wire names now match as_str.
- phoebus-executor::install: resolve_explicit (no model, no fallback),
resolve_deterministic and resolve_with_ai; validate_proposal re-resolves the
candidate against real metadata, rejects fabrication/ambiguity/staleness/
duplicates, maps it to the existing broker action, and binds approval to a
digest; revalidate + verify_installed. chooser gains per-lane friendly-name
resolution and structured evidence.
- transaction::begin/finish record an in-progress transaction before mutation.
- sys: --portage/--flatpak/--nix/--snap/--appimage/--ebuild (mutually
exclusive) bypass the model; an unqualified install consults the model and,
with none, prints the deterministic selection and installs nothing.
- The installer persists /etc/phoebus/install.toml; sys loads it and adds free
space, Wayland, usable lanes, saved preferences and recovery capability to
the bounded facts.
- Docs: ADR 0013, docs/SYS.md install sections and cases 23-31, CHANGELOG,
STATUS, HANDOFF, ROADMAP. New live-VM workflow check script.
Host gates pass: fmt, clippy (no new warnings), workspace tests, make test.
VM: verified the workflow CLI and read-only investigation on the reference
LiveGUI ISO; a full target install journey is running (see HANDOFF).
The installed-target check scanned only the top level of /boot and /efi for
vmlinuz/kernel. With layout=bls, kernel-install places the kernel as
<boot>/<machine-id>/<version>/linux, so a correct install would have been
rejected. Scan the tree (bounded, without following symlinks) for linux/vmlinuz/
kernel, and accept a BLS entry that names a kernel.
- add policy tests for missing hardware information, limited storage choosing
the smaller candidate, and the same application resolving to Portage binary,
source or Flatpak depending on the machine, preference and sandbox
requirement.
- drop the always-on strong-sandbox bonus to a mild +3 so GUI apps are not
effectively routed to Flatpak by category (ADR 0006 revision intent).
- keep the assistant prompt and a plan-acceptance test in sync with the
extended action schema (choose_package, set_package_preference, snap_*,
appimage_acquire, custom_ebuild_prepare).
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).
Record the reliability pass across STATUS, HANDOFF, CHANGELOG, ADR 0012,
the live README and the boot-verification log: the deterministic live GPU
decision with a real nouveau fallback, the 580 legacy cap and mixed
open/proprietary incompatibility, the compatibility verifier, the
installed lifecycle fix, the repaired GUI harness, the automated but
unrun rollback gate, and the scoped live sudoers. Withdraw the stale
handoff claim that the gui_bridge tests hang (the workspace suite
passes) and record the installed-target missing-sys gap.
The live user had NOPASSWD: ALL for the graphical broker. Replace it with
an emitted, visudo-validated policy that grants unattended escalation only
to /usr/local/bin/phoebus-installer, /usr/local/bin/sys and the systemctl
power actions; no ALL, no sh -c and no wildcard. The recovery console is
preserved: it logs in with the live-only password and authenticates sudo.
build.sh installs the asset, validates it with visudo and refuses any
unscoped policy. The GUI harness stages its preseed config with the
password-authenticated sudo over a 0600 file instead of bare install, and
the read-only greetd check no longer needs sudo.
Add a serial-driver rollback mode and guest scripts that exercise the real
rollback path: record the /var/db/pkg fingerprint and a /home marker,
create a recovery point with sys snapshot, install a small package as a
controlled reversible update, run sys undo, power off, boot detached and
compare the restored package state and /home against the pre-rollback
values. Checks kernel modules, the snapshot recovery entry and sys
rollback status. sys is fetched from the host, matching the existing
harness evidence procedure; booting the recovery entry offline remains a
documented manual gate. bash -n guards for every guest script are added
to the no-VM unit tests.
The graphical harness still assumed a step-0 welcome, an ERASE field, a
confirmation checkbox, a full-name field and separate passphrase prompts
that were all removed. Update it to the current product:
- navigate with a state-based _goto_step() instead of counting
Return/Ctrl+Right from a step that no longer exists;
- drive the real account fields (username, computer name, password,
confirm) with the default single-password encryption, leaving the
hidden passphrase fields alone;
- trigger the direct "Install now" action and drop the ERASE/confirm
assertions, while still exercising duplicate submission;
- report stage, elapsed time and the last state on an install timeout;
- boot with the single-password disk passphrase (user password) and fall
back to the separate passphrase, instead of always using LUKS_PW;
- remove the dead SESSION_SETTLE knob.
The installer wrote dracut force_drivers naming nvidia modules during the
first kernel build, before the driver package existed, so the initial
kernel/initramfs build could not resolve them. Only the NVIDIA install
stage installs the driver and regenerates the initramfs.
- dracut_conf() no longer emits the NVIDIA fragment; the modprobe policy
is still written before the kernel.
- write_nvidia_dracut_conf() writes it in the NVIDIA stage, after emerge
and before kernel-install add-all.
- verify_nvidia_modules() proves the driver actually built modules for a
kernel and fails the install otherwise; it returns the resolved version
from var/db/pkg so the record carries the real version, kernel and
module names rather than a 'current' label.
- The update path verifies the rebuilt modules before reporting success;
previous kernels and module trees are left in place.
The verifier accepted one-byte placeholder modules, a caller-supplied
version/flavor, any NVIDIA firmware file and a nouveau blacklist that
happened to exist somewhere. It now establishes what it claims:
- reject placeholder modules and userspace libraries (size floor);
- require every module to be registered in the live kernel's modules.dep;
- normalise the dpkg revision and require the userspace libnvidia-glcore
and firmware directory versions to match the bundled driver;
- infer the module flavor from the on-disk naming and reject a
contradiction;
- require the exact etc/modprobe.d/phoebus-nvidia.conf with nouveau
blacklist and nvidia_drm modeset, not any blacklist;
- keep every filesystem read rooted inside the build root.
Negative tests cover placeholders, version mismatches, a stale
modules.dep, a contradictory flavor and a missing final config.
NVIDIA's 580 series is the last to support Maxwell/Pascal/Volta, and
Blackwell requires the open kernel modules. The policy previously masked
>=595, which permits branches that already dropped those architectures,
and assumed the oldest card's branch could serve every newer card.
- Mask >=x11-drivers/nvidia-drivers-581 for the proprietary branch (the
first series after the last supporting one).
- Compute compatibility across the whole device set: Blackwell plus a
proprietary-only GPU has no single branch and is reported as an
explicit incompatibility (nouveau) instead of installing a driver that
cannot accelerate one card.
- Pascal + Ampere remains proprietary and supported (Ampere accepts
either flavor).
The live load script previously modprobed the NVIDIA stack for any PCI
vendor 0x10de and the build required etc/modprobe.d/phoebus-nvidia.conf
that nothing created. Replace the vendor-name check with a deterministic
decision computed from the actual display controllers and the bundled
branch's capabilities:
- phoebus-core gains live_nvidia_plan(): supported GPU -> load the
bundled accelerated stack; unsupported GPU -> explicit nouveau
fallback; no GPU -> leave auto-detection; fail-safe -> load nothing.
- phoebus-installer --live-gpu-plan scans sysfs (overridable for tests)
and prints stable key=value lines; probe_nvidia_display_devices() only
considers display-class NVIDIA functions.
- phoebus-nvidia-load consults it, falls back to nouveau on an
unsupported GPU or a failed accelerated load, and never fails the
unit; the service honours phoebus.nvidia=off.
- build.sh now creates the live modprobe policy, replaces Debian's
unconditional nouveau blacklist, and marks the fail-safe entry.
- Streamline installer to direct 6-step flow, eliminating Step 0 duplicate welcome
- Parse friendly layout names from evdev.lst and sort top 30 world layouts first
- Enable dynamic live keymap switching via localectl on layout selection
- Auto-detect timezone and close sibling combos on dropdown expansion
- Remove redundant keyboard test modal from welcome application
- Default-enable single-password disk encryption and accept passwords under 8 chars
- Replace ERASE typing confirmation with direct 'Install now' action
- Enforce Mango desktop, Btrfs filesystem, and Flatpak/Nix invariants against AI mutation
- Add loopback OpenCode/Ollama auto-detection and humanized failure screen with Retry
- resolve the NVIDIA branch and kernel-module flavor from PCI device IDs
(Turing+ open modules; Maxwell/Pascal/Volta proprietary, masked below 595;
Fermi/Kepler fall back to nouveau, reported; unknown IDs reported)
- capture pci_id/pci_address in the probe; drive VIDEO_CARDS, package.use,
package.accept_keywords, package.mask, modprobe.d and dracut from the plan,
preserving hybrid Intel/AMD
- add the nvidia_drivers install stage (after the kernel, before boot) that
emerges the driver, regenerates the initramfs, records /etc/phoebus/nvidia and
fails the install on failure; sys update rebuilds modules and the initramfs
- refuse AI changes to x11-drivers/nvidia-drivers
- live ISO: signed non-free components, stable-kernel pin (testing 7.2 breaks
the 550 driver), DKMS build for the exact kernel, gated pre-greetd load,
fail-safe entry, gpu-report, and a --verify-live-nvidia build gate that runs
on cached rootfs builds and fails on any missing component
- docs: ADR 0012, STATUS/CHANGELOG/HANDOFF, live README
- also carries the pending OpenCode model-variant/streaming changes and fixes
the GUI bridge install thread join that could hang
Update the changelog, status, handoff, verification register and VM boot
record with the 2026-09-22 graphical journey work: the fixed step sequence,
the interaction-defect fixes (readiness refresh, catalog sync/staleness, AI
revalidation, keyboard suggestion navigation, truthful keyboard-step label,
link vs service readiness, busy/failure handling), the new gui-install
harness mode, and the final-ISO results.
The gui (28/28) and opencode (18/18) journeys pass; gui-install passes every
journey assertion and starts a real install, but the four-hour harness timeout
fired during the kernel build (base packages ~116 min), so two completed
fresh-disk graphical installs + detached boot remain BLOCKED on host build
time, not on a code defect.
Rework the graphical installer into a fixed first-time-user sequence
(Welcome, Language and keyboard, Internet and readiness, AI connection,
Destination disk, Account and encryption, Review and confirmation,
Installation, Completion) with configuration, validation, plans, approval
and execution still authoritative in Rust.
Fix the audited interaction defects: readiness `Re-check` is a read-only
probe that no longer resets the step or clears the disk; model catalogs are
fetched after syncing the edited settings and credentials and stale replies
are ignored; editing a connection field invalidates the validated state;
suggestion lists support arrow/Enter/Escape with a visible highlight and
accessibility; the keyboard step labels the live-session limitation
truthfully; readiness separates the local link from reachable install
services; and busy states always clear, with the bridge failing outstanding
requests when the backend exits.
Add human-readable language/keyboard names, an explicit AI change review
(Accept/Discard), backend-fact review with edit links, real stage progress
with elapsed time and activity, and clearer failure and completion guidance.
Extend the VM harness with a `gui-install` mode that drives the whole
journey through the visible controls, plus regressions for readiness
refresh, disk survival, keyboard suggestion selection and AI invalidation.
Add Rust tests for readiness, the network probe, error kinds and labels.
A fully-validated OpenCode install was refused at the final step because
selecting a disk or setting the account/LUKS secrets cleared the AI
validation. Bind the validation to a digest of only the AI connection
settings: non-AI config changes preserve it, while an AI provider/model/
endpoint/server or AI-credential change invalidates it. Add regression
tests and password-length placeholder hints.
The region and keyboard fields were free-text, so users had to know zone
names and layout names from memory, and the AI model had to be typed.
Add an 'options' bridge op (live timezones/locales/keymaps) and an
'ai_catalog' op (the OpenCode provider/model catalog, or an
OpenAI-compatible /models list), and a searchable PhoebusCombo picker.
Also name provider/model in OpenCode errors instead of an opaque HTTP
code. Record the user-trial findings U1-U5.
Add an 'opencode' harness mode with a guest-loopback relay (the tunnel
shape), keyboard selection of the OpenCode chip, UI entry of the server/
provider/model (and a 0600 server password), and assertions on the
frontend's secret-free state (tested, validated, applied). Record the VM
evidence and the remaining not-run full-install gate.