Valix is designed to run on recent x86-compatible machines and is intended to be a general-purpose desktop operating system. The main goal of Valix is to function as a testbed for certain new or unconventional designs.

Based on the idea that software is more flexible than hardware, Valix runs no binary applications. Instead, applications are executed by an interpreted smalltalk-like language built into the kernel, which gives the kernel greater control over security. This allows us to ignore hardware memory protection; in fact Valix uses a flat physical memory model instead of the more common virtual memory strategy. Because the interpreted language is not allowed to directly touch the system memory, any leak or access violation is the fault of the kernel. In this case, it is better that the system fail obviously rather than hide any system flaw.

Valix also minimizes context switching of any kind. All processes are executed in kernel mode (ring 0). This eliminates the overhead required to switch between userland and kernel space, and eliminates the need for a complicated system call interface.

Valix will not use the traditional filesystem heirarchy based on folders, instead opting to use a system based on heirarchial tag types. Tags may be created as sub-tags; adding a sub-tag to a file implies the file also is tagged under the parent tag. There are many potential intuitive graphical interfaces that could be realized with such a system.

The system will be designed to be very GUI-oriented with a focus on vector graphics. SVG, or perhaps an extension of SVG, will be used in GUI design. Fonts will be stored in the newly created SVG Font standard.

The Valix project is looking for developers who are competant in the C programming language, regardless of former experience with operating systems. We also appreciate help in the form of documentation, advice, artwork, donations, and webhosting.