fruix/docs/PROGRESS.md

Progress

This file is now intentionally compact.

Detailed chronological history through Phase 18.2 has been archived at:

• docs/reports/progress-log-through-phase18-2-freebsd.md

For a broader narrative summary, see:

• docs/PROG_SUMMARY.md

Current status

Fruix currently has:

• declarative system modeling on FreeBSD
• content-addressed system closures under /frx/store
• native FreeBSD base artifacts in /frx/store
• declarative FreeBSD source objects and source materialization
• source-driven native base builds from materialized source snapshots
• side-by-side source revisions and boot validation
• a host-driven non-interactive install path:
  • fruix system install
• a bootable Fruix-managed installer environment:
  • fruix system installer
• a bootable Fruix-managed installer ISO:
  • fruix system installer-iso
• an explicit installed-system generation layout under:
  • /var/lib/fruix/system
• explicit installed-system retention roots under:
  • /frx/var/fruix/gcroots
• a validated installed-system generation switch/rollback workflow via:
  • fruix system status
  • fruix system switch
  • fruix system rollback
• a validated separate in-system development environment overlay via:
  • /run/current-system/development-profile
  • /run/current-development
  • /usr/local/bin/fruix-development-environment

Validated boot modes still are:

• freebsd-init+rc.d-shepherd
• shepherd-pid1

The validated Phase 18 installation work currently uses:

• freebsd-init+rc.d-shepherd

Latest completed achievement

2026-04-05 — Phase 20.1 completed

Fruix now has a validated real-VM path where a booted Fruix-managed FreeBSD system exposes a separate development environment for native base work without collapsing the runtime/development split.

Highlights:

• operating-system declarations now support:
  • #:development-packages
• system closures can now carry a separate development profile at:
  • /run/current-system/development-profile
  • /run/current-development
• opt-in systems now ship an in-guest helper at:
  • /usr/local/bin/fruix-development-environment
• the validated Phase 20.1 guest path exposes:
  • native headers
  • usr/share/mk for bsd.*.mk
  • Clang toolchain commands such as cc, c++, ar, ranlib, and nm
• the validated guest workflow now supports:
  • eval "$(/usr/local/bin/fruix-development-environment)"
  • direct compilation with the Fruix-provided toolchain
  • a simple bsd.prog.mk build on the running Fruix guest

Validation:

• PASS phase20-development-environment-xcpng

Reports:

• docs/system-deployment-workflow.md
• docs/GUIX_DIFFERENCES.md
• docs/reports/phase20-development-environment-freebsd.md

Recent major milestones

• 1d00907 — Add Fruix bootable installer environment
• 2517710 — Add non-interactive Fruix installation flow
• 02a02e3 — Document Fruix FreeBSD source policy
• 865012e — Boot Fruix from distinct FreeBSD source revisions
• 8150508 — Validate side-by-side FreeBSD source revisions
• 5cbf5b9 — Build native bases from materialized FreeBSD sources

Active constraints

• local bhyve remains blocked under Xen due to lack of nested VT-x exposure
• XO self-service creation is still not usable with the current token
• real XCP-ng validation must continue to use:
  • VM 90490f2e-e8fc-4b7a-388e-5c26f0157289
  • approved A/B VDIs:
    • 0f1f90d3-48ca-4fa2-91d8-fc6339b95743
    • 7061d761-3639-4bec-87f7-2ba1af924eaa
• local QEMU/TCG validation keeps conservative default SMP settings; QEMU_SMP remains overrideable

Next step

Per docs/PLAN_4.md, the next planned step is:

• Phase 20.2 — run host-initiated native base builds inside a Fruix-managed environment

Phase 20.1 is now complete: Fruix validates a separate in-system development environment for native FreeBSD base work on the approved real XCP-ng path.