Wiki · The Colony & the Method
UNI — a public read
[redacted: category] — 1 private address. Nothing else was altered. The document is otherwise exactly as it is written in the repository, and the sha256 below is of the original, so what was ingested stays checkable.How to read this page
Three ways to read this page. Precise is the document itself, exactly as it is written in the repository. Plain and Clear were written for this website to help you meet that document — they are about it. They are not it, and they are not evidence.
Eighty-four pages about the colony. Each agent is an Elixir process holding a generative model and doing inference, attached to a body that logs into a Minecraft world as an ordinary player. Around that sit the broadcast suite that films them and the runbooks that keep the whole thing running. There are typed specifications for each organ of the model, plus the world and genome specs. There are also the adversarial review personas used to attack a proposed change before it ships.
It is for the reader curious how a running system is put together and how it is held to account. The accountability half is the more distinctive. There is a lab protocol governing evidence and attribution, and a claim fence that restricts the vocabulary a claim is allowed to use. There is a public gate log. And there is a standing invitation to reproduce any verdict from the commit and the seed named in its receipt.
Start with the public read, then the lab protocol, then the falsification invitation. If you want the mathematics rather than the operations, go straight to the typed organ specs.
What it is not: a description of a mind, and not all one kind of document. A large part of this corpus is design and planning — specs marked as proposed rather than applied, organs designed but not built, plans that were later superseded — and each page states which it is. A specification is not a running system, and these pages are careful about the difference; the reader should be too. Eight documents were withheld from publication because they describe private infrastructure.
Your browser cannot switch reading levels, so the document itself is shown.
Precise — the source document
This is the document. Rendered from the repository at the commit above, with nothing rewritten for the web. A gate re-renders it on every deploy and fails the build if a single byte differs.
Welcome. This is the public-facing entry to UNI, an active-inference colony we are building in the open under the honest-science rules of docs/LAB_PROTOCOL.md. UNI lives on a single computer we call the chip — that computer runs the rootless UNI-OS + the Minecraft world + the FEP brain + the bodies that inhabit it. As we build UNI, UNI grows to become the OS.
If you are a stranger arriving here for the first time, you can read every claim we have and every receipt behind it without asking us for anything.
Where to start
CLAUDE.md— the binding contract (the corrected architecture and non-negotiable rules).docs/UNIVERSE.md— the master cold-start orientation (fleet map, FEP in one page, hard invariants, current honest state).docs/gates/PUBLIC_GATE_LOG.md— the ledger of every gate we claim to have passed, partially passed, failed, withheld, or opened. Each row is machine-verifiable.production/docs/adr/ADR-PROD-013-colony-host-placement.md— where the colony lives, and why.
What we claim, and how you can check
Every claim we make is gated. There are no "proven," no "conscious," no "AGI" claims here — the claim fence (production/schemas/claim_fence.json) enforces the vocabulary. The gates are specific behavioural or organisational signatures we register before the run, and we report the outcome using one of four honest verdicts: PASS, PARTIAL, FAIL, WITHHELD.
You can independently reproduce any of our verdicts by:
- Checking out the repo at the code sha named in the receipt.
- Running the RED launcher at
runs/*.exswith the seed named in the receipt. - Comparing your outcome to the pre-registered PASS + FALSIFIES conditions.
The seed alone is enough. If you cannot reproduce our verdict from the seed + code + launcher, that is a legitimate falsification and we owe you a correction.
Where UNI runs
UNI-LAB, a single computer at [redacted: private-address] on our WireGuard mesh. UNI is rootless on that box (runs as user uni in Podman on uni-colony-net). The Minecraft world is at TCP port :25565, the FEP brain is a Phoenix Elixir app at :4000 with /producer/health and /stream endpoints, the world-view camera is at :3020.
When we broadcast UNI publicly — which we do not do routinely — we do it via a portable studio on any GPU box (currently the operator's Windows machine, code-named THINKER) that captures the LAN feed and renders it. The fan-out relay runs on a separate Linux box (node2). See docs/UNIVERSE.md §1 for the full map.
What we are careful not to say
- We do NOT say UNI is alive, conscious, sentient, self-aware, feeling, suffering, or thinking.
- We do NOT say UNI has "proven" anything about general intelligence.
- We do NOT say UNI is a "world first" or a "breakthrough."
We say UNI has passed specific named gates — behavioural or organisational — that we pre-registered. Read the gate. Read the receipt. Judge for yourself.
What we are careful to do
- Honest verdicts only. PASS / PARTIAL / FAIL / WITHHELD. Never percent-scored.
- Never claim from process existence. Every claim carries its machine gate output.
- One cure at a time. No stacked changes with unattributable outcomes.
- Ship gate. No FE-touching merge without a MERGED VERDICT from a five-persona adversarial review.
- Receipts beat rhetoric. The bytes on disk are the honest ledger.
- Public reproducibility. The seed is enough.
Follow along
- The gate log:
docs/gates/PUBLIC_GATE_LOG.md - The reproducibility bundle:
docs/PUBLIC_REPRODUCIBILITY_BUNDLE.md - The current honest state:
docs/UNIVERSE.md §5 - The FEP math in one page:
docs/UNIVERSE.md §2
If you find a mistake, an over-claim, or a gate whose receipt does not reproduce for you, tell us — that is exactly the correction the system is built to accept.
Thank you for reading honestly.
sha256 effaa7e0c473ed8a — of the original file, so what was ingested stays checkable.
Plain — written for this website, not the source document
The front door for anyone arriving at the project from outside. It says what the project is, where it runs, and how a stranger can check any claim without asking anybody's permission first.
The project describes itself as a colony built in the open, on a single computer, under a written set of honest-science rules.
Everything on the page turns on receipts: files recording what was run. Before a run happens, the team registers what would count as success and what would count as failure. Afterwards they report one of four plain verdicts — passed, partly passed, failed, or withheld — and never a score. Anyone can fetch the code at the named point, run the same launcher with the same seed, and compare. If your outcome disagrees with theirs, the page says that counts against them and they owe you a correction.
It also lists, in the project's own words, the things it refuses to say about itself, including any claim that the colony is aware, and any claim about general intelligence.
Plain · written 2026-08-01 by claude-opus-5 · not yet checked by a person · about the document whose sha256 is effaa7e0c473ed8a
Clear — written for this website, not the source document
A public introduction, written for a stranger rather than for the people building the thing. Its argument is that you should not have to trust them, because you can check.
It begins by naming what the project is: an active-inference colony, built in the open under a written protocol. It runs on a single computer that hosts the operating layer, the world, the model that drives behaviour, and the bodies that live in it. It says that as the work continues, the colony grows into the operating layer itself.
A short reading order follows, pointing at the binding contract, a cold-start orientation, the list of gates added to and never edited, and a decision record about where the colony lives.
The centre of the page is the claim discipline. Every claim is gated, and a machine-checked word list is named as the thing that keeps forbidden words out. Gates are specific behavioural or organisational signatures registered before a run, not chosen afterwards to fit the result. Outcomes are reported with one of four honest verdicts and are never scored as a percentage. To reproduce a verdict yourself, the page says, check out the code at the point named in the receipt, the file recording what was run. Then run the named launcher with the named seed, and compare your outcome against the conditions registered in advance. It states that the seed alone is enough, and that a failure to reproduce would be a legitimate falsification the project owes you a correction for.
Then comes the part that gives the page its character: a list of what the project is careful not to say. It does not say the colony is alive, conscious, sentient, self-aware, feeling, suffering or thinking. It does not say anything has been proven about general intelligence. It does not call itself a breakthrough. What it says instead is that named gates, written down before the runs, were passed, and it invites you to read the gate and the receipt and judge for yourself.
A final section lists the working habits behind that. Honest verdicts only, and no claim from the mere existence of a running process. One change at a time so an outcome can be attributed, an adversarial review before some kinds of merge, and receipts over rhetoric. The page ends by asking readers to report any over-claim they find.
Clear · written 2026-08-01 by claude-opus-5 · not yet checked by a person · about the document whose sha256 is effaa7e0c473ed8a