Nexus Foundry
Forge your own sovereign system. Pick an edition, add drivers, set constraints, and produce proof-carrying artifacts.
What Is the Foundry?
The Foundry is the build pipeline that transforms a KDL recipe into a bootable, provenance-tracked operating system image. It is not a distro; it is a factory.
Current CLI status: the Micro development proof path can emit a bootable demo artifact with signature, BOM, and proof sidecars. The production Forge pipeline for reproducible recipe builds and registry publication is still planned.
Writing Recipes
A recipe is a KDL manifest:
kdl
edition "NEXUS_MECH" {
target "aarch64-virt"
kernel {
scheduler "harmonic-hard"
memory "locked"
}
modules {
include "nip:drivers/imu/bno055"
include "nip:drivers/lidar/velodyne"
include "nip:lib/kinematics"
exclude "nip:net/*"
}
constraints {
no_heap = true
max_boot_ms = 500
}
}Forge Output
| Artifact | Description |
|---|---|
.img | Bootable disk image |
.npk | Self-contained package archive |
bom.json | Bill of Materials with dependency tree |
.proof | ProvChain attestation of the build |
Pricing Tiers
| Feature | Open (Free) | Foundry ($49/build) | Citadel (Contact) |
|---|---|---|---|
| Stream | Rolling | Quarterly freeze | 10-year LTS |
| Recipe builder | CLI | Visual + CLI | On-prem visual |
| Build runners | Local only | Cloud + local | Cloud + on-prem |
| Signed output | Development sidecars today; production signing planned | Planned | Planned |
| Indemnity | — | — | Included |
Next Steps
- Writing Recipes — KDL manifest syntax and constraints
- Build Pipeline — How the Forge resolves, compiles, and signs
- Trust Badges — What each badge means and how to earn them