Skip to content

Glossary ​

Key terms used throughout Nexus OS documentation.

Core Concepts ​

TermDefinition
RumpkThe Nexus sovereign unikernel kernel. Zig HAL + Nim logic. 280KB. The kernel boundary is a protocol, not a syscall ABI.
RumkvType-1 hypervisor layer operating at EL2 (ARM64), Ring-1 (x86), or M-Mode (RISC-V).
ION RingLock-free single-producer/single-consumer ring buffer used for all IPC.
Kernel ProtocolThe stable contract between userland and kernel: typed ION Ring packets, signed BKDL descriptors, and capability verbs. The application-facing surface.
Trap ABIThe CPU-facing entry layer (ecall / svc #0 / syscall). Implementation detail of how the protocol is mechanically submitted; allowed to change per architecture.
SysTableThe Trap-ABI entry surface at a known physical address (0x83000000 on RISC-V, 0x50000000 on ARM64). 136 bytes. Carries ION ring descriptors + fast-path function pointers + framebuffer info.
FiberCooperative execution context within the kernel. Not a thread — no preemptive multitasking at kernel level.
MembraneThe libnexus.a compatibility layer. A "biosuit" that wraps POSIX calls and routes them through sovereign abstractions.
ProvChainCryptographic audit ledger using BLAKE3 + Ed25519. Records every boot, module load, and state change.
GraftingStrategic borrowing of code from Linux/BSD ecosystems, wrapped in sovereign abstractions and security constraints.
SovereignizeThe process of replacing grafted foreign code with native Nexus implementations.
Liquid ComputingThe architectural paradigm of recipe-driven, adaptive operating systems. Liquid Computing has no mandatory kernel, no mandatory execution architecture, and is plural — many different OS architectures can be produced under it. Nexus OS is one such architecture; others are conceivable. See The Three Layers for the relationship between paradigm (Liquid Computing), mechanism (Nexus Forge), and product (Nexus OS).
Nexus ForgeThe build pipeline and factory mechanism that turns a KDL recipe (Recipe + Modules + Target) into a bootable, provenance-tracked Nexus OS image. Embodies the Liquid Computing paradigm concretely. The doctrine is Graft. Evolve. Sovereignize. See The Liquid Computing Philosophy for the full doctrine and Foundry for the current build pipeline.
Nexus OSThe concrete sovereign operating architecture produced by the Nexus Forge under the Liquid Computing paradigm. Has strong opinions: Rumpk (kernel), ION (IPC), NexFS (storage), Cellular Memory, Harmonic Scheduler, Pledge security, Membrane. One of many possible Liquid Computing implementations, but currently the flagship. See What is Nexus OS? for the public overview.

Package Taxonomy ​

TypeNamePurposeExample
NPSNip SensorSingle-purpose sensor firmwareTemperature probe
NPLNip LibraryDrivers and filters in isolated VMsWiFi driver, printer driver
NPXNip eXtensionHot-loadable hooks (eBPF replacement)Packet filter, tracing
NPMNip ModulePure logic librariesOrbital math, crypto
NPKNip PackageEnd-user applicationsFirefox, KDE
NPINip InterfaceAPI bridgesHTTP adapter, gRPC

Isolation ​

TermDefinition
NipCellLightweight isolation container. GoboLinux-style symlink isolation. The "Flatpak killer".
NexterHeavy container using namespace/jail/VM-based isolation. KDL blueprints replace Dockerfiles.
CSpaceCapability space. 64 slots per fiber. Each slot holds a typed capability (channel ID + permission mask).
PledgeOpenBSD-style capability restriction. One-way ratchet — once pledged, permissions can only shrink, never grow.
UnveilFilesystem visibility restriction. A process can only see paths it has been explicitly granted access to.

Security ​

TermDefinition
Capability AlgebraThe 7 primitive operations: SPAWN, SEND, RECV, MAP, MASK, TICK, GRANT.
Law of DecayCapabilities degrade over time and delegation depth. Prevents privilege accumulation.
Kinetic EconomyEnergy-budget rate limiting. Every operation costs energy. Prevents DoS by exhausting budgets.
TOFU+Trust On First Use with key pinning. Initial trust establishment for network peers.
AirlockQuarantine zone for untrusted code. New modules enter the airlock before being granted system access.

Storage ​

TermDefinition
NexFSThe Nexus filesystem. Dual-axis design: storage class (Atom/Sovereign/Archive) × network scope (Local/Cluster/Federation).
CASContent-Addressable Store. Files addressed by their BLAKE3 hash, not by path.
CDCContent-Defined Chunking. Files split at content boundaries for efficient deduplication and sync.
DAGDirected Acyclic Graph. Version history stored as a Merkle DAG for efficient branching and merging.
TimeWarpInstant filesystem snapshots using copy-on-write DAG nodes.
Sovereign FSHThe Nexus filesystem hierarchy: /Cas, /Nexus, /Cell, /Bus, /Data. Replaces POSIX FHS.
Block ValveThe kernel's storage interface. The kernel passes sectors; it does not interpret them.
BAMBlock Allocation Map. Tracks free/used blocks in NexFS.

Network ​

TermDefinition
NetSwitchKernel-level L2 packet demuxer. Routes frames by EtherType to the correct ION Ring.
UTCPUnikernel Transport Control Protocol. Identity-centric, NACK-based sovereign transport. EtherType 0x88B5.
LWFLibertaria Wire Frame protocol. EtherType 0x4C57. Part of the Libertaria protocol stack.
CellIDSipHash-128 identity used by UTCP. Nodes dial by CellID, not IP address.
LwIPLightweight IP stack, grafted from the open-source project and running in userland (Membrane).

Build System ​

TermDefinition
KDLConfiguration language used for recipes, manifests, system blueprints, and service definitions.
BKDLBinary KDL. Packed manifests embedded in ELF sections for boot-time parsing.
STCStandard Template Construct. A system profile definition (Tiny, Micro, Core, Fleet, Unikernel).
BEBBoot Extension Block. Updatable microcode that extends Rumpk without modifying its frozen core.
Variant-CIDCryptographic content identifier that uniquely identifies a specific build variant of any artifact.

Display ​

TermDefinition
Surface ManagerSovereign compositor. Zero-copy rendering, 120Hz Photon scheduling.
HUDHeads-Up Display. Visual filesystem interface mounted at /Bus/hud/.
SSPSurface Submission Protocol. How applications submit frames to the compositor.

Scheduling Spectrums ​

SpectrumDeadlineUse Case
Photon2msInterrupt handlers, DMA, real-time I/O
Matter10msNetwork processing, input events
Gravity50msBackground computation, housekeeping
VoidUnlimitedIdle tasks, opportunistic work