A Note from the Developer
Building with intention
HORUS OS is an ongoing attempt to build a Linux distribution around a simple idea: the experience of using an operating system deserves the same consideration as the engineering that makes it work.
A distribution is more than an installer, a collection of packages, or a desktop environment. It is the result of many interconnected decisions — how the system boots, how software is provisioned, how the desktop behaves, how the visual language is applied, and how the whole system can be maintained over time.
HORUS OS is being developed with those decisions in mind.
Why build another Linux distribution?
Linux already offers an extraordinary range of distributions, desktop environments, and tools. HORUS OS is not an attempt to suggest that the existing ecosystem is missing something essential, nor is it a claim that another distribution is inherently better.
It is an engineering project: an opportunity to explore how a system can be assembled, refined, documented, and presented as a coherent whole.
That means paying attention not only to what works, but also to how it works, why a particular approach was chosen, and whether it can be maintained as the project grows.
Engineering before appearances
A polished desktop can make a strong first impression, but appearance alone does not make a reliable operating system.
The underlying work matters: repeatable ISO builds, predictable boot behavior, a functional live environment, a dependable installation workflow, and careful validation of the resulting system. These foundations need to be established before the project can make meaningful claims about readiness.
HORUS OS is currently in development. Its roadmap reflects the engineering work still required, rather than presenting planned features as finished accomplishments.
The goal is to make progress that can be tested, explained, and improved.
A considered desktop experience
The current direction is based on Arch Linux, with Niri and DankMaterialShell forming the intended desktop experience.
This direction gives the project room to explore a more deliberate relationship between system configuration, window management, desktop interaction, and visual identity. The aim is not to add complexity for its own sake, but to make the parts feel intentional and consistent.
The visual language follows the same principle. Dark surfaces, restrained gold accents, clear typography, and geometric forms provide a recognizable identity without overwhelming the interface.
Design should support the system, not distract from it.
An evolving project
HORUS OS is still being built, and its direction may change as implementation reveals new constraints or better approaches. Some ideas will work as expected; others will need to be reconsidered.
That is part of the process.
The important thing is to keep the project grounded in practical engineering, document its progress honestly, and make decisions that remain understandable beyond the moment they are made.
This website is part of that effort. It provides a place to explain the project, document its development, and eventually share releases when they are ready.
What comes next
The immediate focus is on completing the installation and boot workflow, refining the desktop integration, and validating the system as a whole. Release qualification and compatibility testing will follow as the underlying work matures.
There is still work to do before HORUS OS can be presented as a release-ready distribution. Until then, the roadmap will serve as a record of the work ahead, and this note will remain an account of a project in progress.
HORUS OS is being built one deliberate decision at a time.
This is a starter note. Replace or revise any section to reflect your own voice, motivations, decisions, and current development status.