A desired state system wraps a mutable, imperative…

A desired state system wraps a mutable, imperative interface with a declarative one. The user says how things should be; the system observes actual state, computes the diff, and reconciles — continuously or on demand.

Backlinks

Jenco's framework names the pattern: wrap a mutable, imperative interface with a declarative one, and let a reconciler close the gap. NixOS is the cleanest implementation of this in production. →

What Jenco calls a desired state system is closed-loop feedback control applied to software: the sensor is state observation, the comparator is diff, the actuator is the API call. →

Desired State Systems A desired state system wraps a mutable, imperative interface with a declarative one. The user specifies what should be; the system observes actual state, computes the diff, and reconciles (Jenco). →

GitOps for Fleet Management Fleet v4.65.0 introduced a GitOps mode that puts the UI in read-only. This prevents the classic conflict where UI changes override declared state — ensuring the git repo remains the sole source of truth. This directly addresses the problem of mutable state: wrapping a mutable interface (the UI) with a declarative one (git). →

Continuous Assembly

2039243367905972451 — CA must measure reality to plan changes
2039244345883427238 — the build plan depends on current state, known only at build time
2039309313987187063 — the physical world is the ultimate mutable, imperative system — desired state should work here too
2039308018211586082 — NixOS as a particular case of desired state
2039302841450537164 — desired state wraps mutable with declarative (Jenco)
2039290956810448985 — NixOS: describe what it should look like, not how to get there
2039309916691956045 — desired state as a file inherits the entire text toolchain
2039290263060046285 — GitOps for device fleets: declaring desired state in git

→

Feedback Loops

Controller Pattern — watch, diff, reconcile: the generic loop
Kubernetes Controllers — K8s implementation: many simple controllers via API server (bib)
Perpetual Disequilibrium — the system never settles, and that's correct
2039568269989036219 — desired state systems = feedback control: sensor is observation, comparator is diff, actuator is API call
2039569197378965946 — Kubernetes standardized this: CRDs + controllers for any desired state
2039302841450537164 — desired state wraps mutable with declarative (Jenco)
2039308018211586082 — NixOS as a particular case of desired state
2039290956810448985 — NixOS: describe desired, compute path to it

→

NixOS NixOS is a canonical example of a desired-state system applied to operating system configuration. It wraps a mutable, imperative substrate (Linux) with a declarative interface — the pattern described by Jenco as the general shape of desired-state systems. →