Dubnium Documentation
Use this site as the operator entrypoint for installing, bringing up, and understanding the Dubnium workstation.
Primary target: the NixOS host named workstation. WSL is a headless validation
target for shared modules and docs, not the deployed workstation.
Choose Your Path
- Installing a workstation: start with Fresh Install and Custom Installer USB.
- Bringing up an existing workstation: use First Bring-Up before transition testing.
- Enabling local inference: seed the model with Model Seeding, then follow vLLM Runtime.
- Working on persistent context: start with Persistent Context Memory Architecture, Memory Service, and the Memory Governance Contract.
- Validating in WSL: use WSL Documentation Boundary and WSL Bring-Up.
- Managing flake inputs: use Dubctl Flake Input Manager.
Current Defaults
dubnium.vllm.enable = false: vLLM is opt-in for explicit compute testing.dubnium.plano.enable = false: Plano routing is opt-in until its runtime is installed and validated.- Runtime and user secrets stay outside Nix source. See Runtime Secrets.
- User-level Home Manager configuration comes from
external/dotfiles. - Generated documentation is committed under
web/docs/. - Flake input operations use
dubctl, exposed asnix run .#dubctland installed by default on the workstation.
Install Source Contract
- Installer media labels are
DUB-ISOandDUB-SEED. - Install bootstrap uses local source from media or checkout state, not an install-time GitHub token.
- Post-install source reconciliation is explicit. See Post-Install Source Reconciliation.
Ownership Boundaries
| Owner | Responsibility |
|---|---|
| Dubnium | NixOS system config, workstation services, install media, runtime units |
| Dotfiles | Home Manager user config, user shell, user-level tool configuration |
| Runtime secret provider | Host and user secrets outside the Git-tracked Nix source |
| Model/router repos | Client policy, routing schemas, and model-router behavior |
Sanity Checks
nix flake check
sudo nixos-rebuild build --flake .#workstation
mdbook build
When building docs from Windows, run mdbook build inside the NixOS WSL distro
with mdbook and mdbook-mermaid in the shell.
Known Warnings
mdbook-mermaidmay warn about a minor mdBook version mismatch; that warning is non-fatal when the HTML backend finishes successfully.- vLLM runtime setup should avoid broad PyTorch, audio, JAX, or TPU extras unless they are explicitly required.
Start Here
Local Inference
Memory System
- Persistent Context Memory Architecture
- vLLM Persistent Memory Prototype
- Memory Service
- Memory Data Model Specification
- Memory Governance Contract
- Anthesis Memory Envelope Examples
- vLLM Memory Phase 1 Plan
- Memory Phase 2: Governed Structured Memory
Architecture
External Sources
- ryjen/dotfiles
feat/nix-migrationis checked out atexternal/dotfilesand owns user-level Home Manager configuration.
Local Docs Viewer
This repository includes mdBook config for local browsing only. mdBook is not a Dubnium OS dependency and does not need to be installed in the target system configuration.
nix shell nixpkgs#mdbook nixpkgs#mdbook-mermaid
mdbook serve --open
Generated output goes to web/docs/.
Decisions
- ADR-0001: Runtime Switching First
- ADR-0002: Studio-Local Is a Desktop Overlay
- ADR-0003: vLLM Is Compute-Only in V1
- ADR-0004: Boot Defaults to Desktop
- ADR-0005: k3s Stays Stable Across Modes in V1
- ADR-0006: Tailscale Platform Connectivity
- ADR-0007: WSL Is a Headless Validation Target
- ADR-0008: Seed Local vLLM Model Bundles
- ADR-0009: Manage Runtime Secrets Outside Nix Source
- ADR-0010: Keep Persistent Memory Separate From vLLM Runtime
- ADR-0011: External Ownership Boundaries
Runbooks
- Custom Installer USB
- First Bring-Up
- Fresh Install
- Post-Install Source Reconciliation
- Laboratory Bootstrap
- Model Seeding
- Runtime Secrets
- vLLM Runtime
- vLLM Persistent Memory Prototype
- Memory Service
- Tailscale
- Transition Testing
- Failed Transition Recovery
- Dubctl Flake Input Manager