Felunyx OS / Foundation
Foundation
The base that keeps Felunyx recognizably Linux: Arch, systemd, rolling release, kernels, and storage.
- Direct Arch Linux base
- Linux Zen + LTS
- Btrfs for automatic installs
Project
This area organizes architecture, decisions, phases, and evidence without making you crawl through the whole repository. GitHub stores the source; the site explains the source.
Understand the system
The constellation is an orientation map, not a dependency diagram. Choose an area to see what it groups together and which decisions support that direction.
Felunyx OS / Foundation
The base that keeps Felunyx recognizably Linux: Arch, systemd, rolling release, kernels, and storage.
Felunyx OS / Install & Recovery
The safe way into and back out of the system: ISO, Calamares, boot, restoration, and recovery without silent repair.
Felunyx OS / Felunyx Platform
The shared backend that keeps the GUI, CLI, and official profiles from becoming parallel systems with different consequences.
Felunyx OS / Packages & Updates
Sources stay visible, system changes become reviewable transactions, and risk is not hidden behind a pretty button.
Felunyx OS / Desktop Experiences
KDE is the first reference; XFCE and Hyprland come later. Official profiles share the platform and an explicit support boundary.
Felunyx OS / Whiskers & Research
Whiskers is the public identity for the native desktop in development, not a shortcut. Research starts from a mature Wayland base and keeps a replaceable Qt/QML shell over Rust policy.
Independent project
The project is developed independently, with priorities guided by what can be tested, documented, and maintained clearly. Contributions are welcome and go through the same review and evidence process.
How we say something works
Remote covers source, contracts, tests, manifests, builds, and CI. Virtual requires boot, installation, reboot, and integration in a VM. Hardware requires the physical world: firmware, GPU, network, storage, peripherals, power, and monitors.
Passing R does not mean passing V. Passing V does not mean passing H.
Where we are
No decorative percentage and no invented release date. The summary below shows where the project came from, the active phase, the next step, and a more distant roadmap point.
establish one canonical understanding of what Felunyx is and how it will be built.
produce a minimal, repeatable, bootable Felunyx image without pretending the full experience exists.
establish the backend shared by every Felunyx experience.
declare only the capabilities the project can maintain.
Choose by question
Start with what you want to find out. Some areas are already public; others stay visible as part of the plan, without fake links.
Phases, current state, and exit criteria.
OpenActivity and component state. Planned for its own subplan.
PlannedHypotheses, prototypes, and preserved rejections.
Open Why does Felunyx look like this?DesignApproved visual system and identity.
Open Can I do X on Felunyx?FAQShort practical answers with links to the right source.
Open How is the system organized inside?AnatomyA guided deep dive into the system parts and how they connect.
Open