01active
Cix
The operating system and control plane: containers, networks, hardware, services and the REST API.
Open repository ↗The initiative behind Cix
Build the system.
Keep it legible.
The Cix Project is the initiative owner for Cix and CBS — keeping the route from source to build to running system open, coherent and accountable.
- Core
- Cix OS
- Build
- CBS / CPDL
- Stewardship
- Open source
PROJECT PROVENANCEv0.1 / LIVE PATH
01 / SOURCEMission, code, decisionsthe public record that makes the system explainable
02 / CBSRecipes into artefactsCPDL, packages and deterministic builds
03 / CIX OSResources in operationworkloads, networks, hardware and services
one route / public artefacts / inspectable state accountable by design
01 / The proposition
Infrastructure should be
explainable end to end.
The Cix Project holds the line between intent and mechanism. That means building the distribution, the build system, the recipe corpus and the release practice as one legible system — with each part public, replaceable and accountable.
02 / A project, not a pile of repos
One system.
Clear boundaries.
Each repository has a job. Together they make a route from a reviewed source change to a running workload.
02active
CBS
Cix Build System. Parses CPDL, executes package phases, and emits verifiable CIXPKG artefacts.
Open repository ↗03active
Recipes
Versioned package, image and deployment definitions: the reviewed input to the build path.
Open repository ↗04active
Cache
Published binary artefacts and signed installers. A cache, never a catalogue or trust boundary.
Open repository ↗The operating system— the place where the project’s principles become an operator’s reality.
03 / What an owner protects
Stewardship is a
technical responsibility.
Keep the contract visible.
Document the resource model, API boundaries, version identity and compatibility honestly. No hidden source of truth.
Make releases verifiable.
Publish keys independently, keep old keys for old artefacts, and make a release reproducible from the source trail.
Prefer durable interfaces.
Use ADRs and tests for hard-to-reverse decisions. Let implementation move without making operators guess.
Grow the contributor path.
Give builders a clear first issue, a working local loop, and a reason to trust that their work can land.
04 / Find your entry point
There is work at
every layer.
Read the source, build a package, improve a guide, or help make the project easier to operate. Start with the contract that matches your curiosity.
The Cix Project