Arch, systemd, Zen + LTS and Btrfs.
The base is rolling Arch with systemd. Zen is the default kernel, LTS stays installed as fallback, and automatic installs use Btrfs with separated system and home scopes.
Felunyx OS
It is not a theme. It is also not an excuse to hide Linux.
Felunyx is a rolling distribution based directly on Arch. The point is to take the freedom already there and build a coherent experience around it: updates, recovery, desktop, GUI and CLI speaking the same language.
In development
System layers
The pretty part only works if the foundation makes sense.
We try to own what changes the experience and reuse mature upstream work where rewriting everything would mostly buy permanent maintenance.
One change, one story.
Packages, risk, snapshots, reboot-pending state and action history should go through the same backend. GUI and CLI expose the same consequences instead of inventing two realities.
No silent “repair magic”.
Recovery follows Analysis → Proposal → Confirmation → Result. Before changing anything, it shows what it found, what it proposes, and which commands/files are affected.
KDE first. The rest without fragmenting the distro.
KDE is the first reference. XFCE and Hyprland arrive after the platform stabilizes; the native DE is long-term work and does not block the first useful release.
Why Arch?
Because we want the foundation, not another layer of distance from it.
Arch brings a huge ecosystem, strong documentation and a rolling model that fits the project. It also means taking responsibility for integration, updates and recovery — exactly the parts Felunyx wants to improve instead of hide.
Want to open it up?
Anatomy starts where the short sentence stops being enough.
Kernels, updates, reversibility, Work Environments and the future DE each get their own page covering intent, architecture, limitations and current status.