Your task is described in ./docs/PLAN_3.md. Current progress is stored in ./docs/PROGRESS.md.

Perform the next step towards the final goal. Update the progress file and `git commit` after each subphase (or even in between, if adequate).

You can use `sudo` freely, install missing software via `sudo pkg install`. If you still miss helpful tooling or other resources, stop and ask the operator, don't work around it.

Guix sources are in ~/repos/guix. FreeBSD sources are installed in /usr/src. Clone other helpful repos or extract sources to ~/repos/ as required.

Note: Our goal is NOT to run Guix on top of FreeBSD, but more like to use it as inspiration for Fruix, which should embrace FreeBSD semantics - in the long run - like jails, bhyve, etc.:

1. The model you want to preserve

This is the real treasure:

- declarative builds
- content-addressed store
- reproducibility
- daemon-mediated privilege separation
- garbage collection from roots
- derivations as build descriptions

That is the soul.

2. The platform assumptions you should challenge

These are not sacred:

- Linux process/container assumptions
- GNU coreutils/bash/findutils as ambient baseline
- specific /proc or signal behavior
- GNU userland quirks in package recipes
- Linux-centric builder environment setup

That is just sediment from history.

Good luck!