Articles

13 written explanations of the system, in the order they should be read. These are the only pages on this site that are authored rather than published.

Why these are different, and why that is risky. Every other page here is a document from a repository, rendered as written — it cannot be wrong about itself. These are prose about code, which goes stale the moment the code moves. So all 59 citations and 15 quoted blocks are resolved against the real files at their real commits when this site is built, and a citation that no longer resolves fails the build. A quoted block is the file’s own bytes, not a transcription.

Start here

What UNI is, in the order you have to meet it. Six ideas, each one needed to understand the next.

4 citations · 1 quoted source block

The colony

A UNI is an Elixir brain, a Node body and a Minecraft player, joined by a pipe that is also a Markov blanket.

5 citations · 2 quoted source blocks

The Producer

The broadcast is not run by a script. It is run by an agent, using the same engine as the bots it films — and its action space includes their birth and death.

6 citations · 1 quoted source block

The control plane

An append-only hash-chained ledger with exactly one writer, five verdict words, and a room whose override does not exist.

9 citations · 2 quoted source blocks

The active-inference brain

Perception as free-energy minimisation, action as expected-free-energy minimisation, and a hard rule about what may enter the logits.

10 citations · 1 quoted source block

The operator plane

Five surfaces for the human in the chair, built on one law — a read never actuates — and one file that logs its own documentation defects.

8 citations · 1 quoted source block

The flagellar motor laboratory

A real bacterium's rotary motor, a deterministic reconstruction of it, and an agent that has to live with the difference. The one place in this estate with licensed microscopy on one side of the boundary and a model on the other.

5 citations

The broadcast suite

How a colony of agents becomes a live public broadcast — the chain to air, the 33 scenes, the run of show, and the seven paths that all refuse to go live.

5 citations · 4 quoted source blocks

Quick start

Fifteen minutes from nothing to a running active-inference engine you can watch think. No accounts, no GPU, no network after the first fetch.

0 citations · 1 quoted source block

Install guide

Every prerequisite with the version the estate actually declares, where each is declared, and the three places those declarations disagree with each other.

5 citations · 1 quoted source block

Run it

Every runnable entry point in the estate, with the command that really starts it, grouped by subsystem, each marked with whether you can actually run it.

2 citations

Maintenance

Watchdogs, boot persistence, health checks, backups, ledger repair and disaster recovery — including the four things this estate knows are not underwritten.

0 citations · 1 quoted source block

How-to recipes

Narrow single-task answers. "I want to X" — each one is a few commands and the reason the order matters.

0 citations

What these articles are careful about

Each one ends with a section saying what is notestablished. That is not modesty — it is the load-bearing part. The estate’s own contract holds that passing software tests is necessary and nowhere near sufficient for a claim about biology, intelligence, or experience, and that observation, reconstruction and simulation may never be relabelled as one another.

Where the articles record a gap — a subsystem with no diagram, a surface with no canonical document, a component with thin tests — that gap is real and was measured, not softened.