Anatomy
Open Felunyx up and see what is actually inside.
This is where we explain distro decisions without making you hunt through commits, PRs and Markdown. Stay at the product idea or keep going into architecture, phase and limitations — your call.
Status stays obvious because a pretty concept does not become a shipped feature through osmosis.
The distro, piece by piece.
These pages mix product and engineering on purpose. First comes the problem we want to solve; then how the architecture tries to solve it without magic promises.
Btrfs alone does not create a safe experience. What matters is knowing when state is preserved, what gets rolled back, and how to return without dragging home data along by accident.
Felunyx treats system change as an understandable transaction: source, dependencies, risk, snapshot, confirmation, execution and result in one story.
Felunyx installs two kernels for a very unglamorous and useful reason: a fallback needs to exist before you discover you need it.
Work Environments is the direction for reopening projects, apps, workspaces and supported preferences without promising to copy arbitrary process memory or guess private state.
Felunyx wants to own what changes the experience and reuse mature Wayland infrastructure where rewriting everything would mostly buy permanent maintenance.