The Three Layers — Liquid Computing, Nexus Forge, Nexus OS

Read this first. The terms Liquid Computing, Nexus Forge, and Nexus OS appear throughout the Nexus docs. They are not competitors and not synonyms — they are three distinct layers in a single architecture of production.

The Three Layers

╔══════════════════════════════════════════════════════════════╗
║                       LIQUID OS                              ║
║                                                              ║
║   The architectural paradigm of recipe-driven, adaptive      ║
║   operating systems. No mandatory kernel. No mandatory       ║
║   execution architecture. Plural — many OS architectures     ║
║   can be produced under it.                                  ║
╚══════════════════════════════════════════════╦═══════════════╝
                                               ║ methodology
                                               ▼
╔══════════════════════════════════════════════════════════════╗
║                       NEXUS FORGE                            ║
║                                                              ║
║   The build pipeline and factory mechanism. Turns a KDL      ║
║   Recipe + Modules + Target into a bootable, provenance-    ║
║   tracked operating system image. Embodies the Liquid Computing     ║
║   paradigm concretely. Doctrine: Graft. Evolve. Sovereignize.║
╚══════════════════════════════════════════════╦═══════════════╝
                                               ║ generates
                                               ▼
╔══════════════════════════════════════════════════════════════╗
║                        NEXUS OS                              ║
║                                                              ║
║   The concrete sovereign operating architecture produced     ║
║   by the Nexus Forge. Has strong opinions: Rumpk, ION,       ║
║   NexFS, Cellular Memory, Harmonic Scheduler, Membrane,      ║
║   Pledge security, Sovereign Init. One of many possible      ║
║   Liquid Computing implementations — but currently the flagship.    ║
╚══════════════════════════════════════════════════════════════╝

Layer	Role	Answers
Liquid Computing	Paradigm	How should an operating system be constructed, adapted, and evolved?
Nexus Forge	Mechanism	How do we actually turn intent into a bootable, verifiable OS?
Nexus OS	Product	What is the actual machine?

The Baukasten Formula

The Forge embodies the Baukasten principle (German for "building block set"):

Recipe
   +
Modules
   +
Target Hardware
   │
   ▼
Forge
   │
   ▼
Operating System

One forge. Many instruments. Each edition enforces hard technical constraints at build time.

Why Three Layers, Not One

Liquid Computing has no mandatory kernel. It could use Linux, Rumpk, seL4, Zircon, a unikernel, or something not yet invented.
Nexus OS has strong opinions. It chose Rumpk, ION, NexFS, Cellular Memory, Harmonic Scheduler, Membrane, Pledge. Those are decisions, not requirements.
Nexus Forge is the bridge between them — it is where Liquid Computing becomes concrete, without locking the concrete into a single architecture.

The three are related by production, not equivalence:

Liquid Computing ──(methodology)──▶ Nexus Forge ──(generates)──▶ Nexus OS
                                              │
                                              └─▶ Sovereign Nexus Components

Analogy

Concept	Biological analogue
Liquid Computing	Biology — defines mutation, adaptation, selection, evolution
Nexus Forge	Evolutionary machinery — takes environment + constraints + material
Nexus OS	A species — has skeleton, immune system, organs, nervous system, DNA

The species is one outcome of the evolutionary machinery. The evolutionary machinery is one implementation of biology. Biology is older than both.

What Each Layer is NOT

Liquid Computing is NOT a kernel, an execution architecture, or a brand split from Nexus OS. There is no "Liquid Computing" product separate from "Nexus OS". Liquid Computing is the doctrine; Nexus OS is the flagship.

Nexus OS is NOT a Linux distribution, a distro-snapshot, or the only possible result of Liquid Computing. Liquid Computing is plural; Nexus OS is singular.

Nexus Forge is NOT a CI system, a package manager, or a single tool. It is the entire build civilization (recipes, modules, signing, registry, mesh) acting in concert.

Silicon-Native Changes the Relationship

The general Liquid Computing paradigm says an OS should be configurable for the machine it runs on. The Silicon-Native direction (SPEC-712, ROADMAP-0.4) takes this further: Nexus OS becomes the first Liquid Computing implementation designed to understand the machine beneath it as a living topology rather than a collection of devices.

Liquid Computing could create:        Nexus OS eventually does:
─────────────────────          ─────────────────────────────
"An OS optimized for ARM"  →   "I see:
                                  12 heterogeneous CPU cores
                                  1 GPU
                                  1 NPU
                                  CXL memory
                                  NVMe topology
                                  PCIe bottlenecks
                                Therefore:
                                  THIS operating system should exist."

That is the difference between an OS that is configurable and an OS that understands where it lives.

The Three Layers — Liquid Computing, Nexus Forge, Nexus OS ​

The Three Layers ​

The Baukasten Formula ​

Why Three Layers, Not One ​

Analogy ​

What Each Layer is NOT ​

Silicon-Native Changes the Relationship ​

See Also ​