Wiki · The Colony & the Method
UNI Minecraft Colony → UNI.OS appliance — migration plan + OS-agent prompt
[redacted: category] — 3 private address, 1 credential. 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.
Status (2026-06-21): the colony is being migrated off Thinker (local PC) onto the UNI.OS appliance, broadcast live as the "UNI.OS Live Workload Migration" world premiere.
- Thinker Minecraft world (
:25565) = paused (graceful stop; world saved). - Thinker OBS stream = up, showing the premiere card over the
:4000glass cockpit. - The bedrock fix (
SP.Brain.MCsurface preference) is in the code and travels with the colony.
Appliance facts (verified via uni-lab MCP)
uni-lab, Dell PowerEdge,phase5_lab_os. 39 GiB RAM (25 free), 5.5 TB disk (5.1 TB free), load ~4.4.- Rootful Podman host. LAN
[redacted: private-address](eno4), WireGuard[redacted: private-address], tailscale. - Already running: biological-builder API
:8000, aion AIF runtime UDP:5515, WSC world-bridge (ready_phase4_wsc_adapters), Prometheus/Grafana, cloudflared, forensic witness. - No colony container present — the colony has never run here.
- Every mutating op (
podman_pull/run/quadlet_apply,nftfirewall viaos_exec) waits on a human approval in the appliance's queue. Data on named volumes or/srv(avoid/var/lib/uni).
Path A — lift-and-shift the colony as containers (now)
Repo: TMDLRG/UNI.MineCraft, branch lab/ozone-life-uni-hard-science. Stack:
- mc-server —
eclipse-temurin:17-jre+mcserver/paper.jar; world seed 8675309;server.propertiesRCON on (:25575passsp),spawn-protection=0. Volume for the world. - uni-colony —
elixir:1.16-otp-26+ the project; runsui/Phoenix (iex --sname uni --cookie [redacted: credential] -S mix phx.server), serves the HUD:4000(/stream,/), reaches mc-server RCON. Carries the surface-preference fix. Pure-Elixir AIF — no Nx/Rust/NIF/port (standing invariant). - uni-bodies —
node:20+viewer/body.js(mineflayer),MC_HOST=mc-server. N bodies. - uni-cam —
node:20+ xvfb + mesa (headless GL) +viewer/director.js(prismarine cam:3020). The headless WebGL context is the one genuinely new piece vs. Thinker.
Deploy: shared podman network so they resolve each other; podman_quadlet_apply (persistent) per
service; open nft for :4000 + :3020 on the LAN so Thinker OBS captures them over the LAN for
the stream (simplest cutover — no headless streaming yet). Verify: colony ticks (mailboxes 0, on the
surface), cam renders, HUD serves. Then OBS points "Colony Cam"/"Glass HUD" at
http://[redacted: private-address]:3020 / :4000 and cuts the program scene back from "Migration" to "Colony Live".
Path B — native convergence (next)
Colony becomes a WSC world on the appliance's own aion runtime (lab_world_register/attach,
worldBridge, UDP :5515) — inference on UNI.OS, not Elixir; headless streaming on the appliance.
The "OS-as-mind" work. OS-agent's core domain.
OS-AGENT PROMPT (copy to the OS agent)
Deploy the UNI Minecraft colony (repo
TMDLRG/UNI.MineCraft, branchlab/ozone-life-uni-hard-science) onto the UNI.OS appliance as persistent Podman services, per §"Path A" above. Build four images (mc-server, uni-colony, uni-bodies, uni-cam — the cam needs xvfb+mesa headless GL), wire them on a shared podman network (uni-colony+bodies+cam reach mc-server by name; RCON:25575passsp; world seed8675309), deploy via quadlets, and opennftfor:4000and:3020on the LAN so Thinker's OBS can capture them during the live cutover. Keep the WSC frozen (worldStateInUShared: rejected), no secrets in the repo, pure-Elixir colony invariant intact. Report: image build results,podman_ps, and a colony health check (agents ticking on a forested surface, mailboxes 0). Then hand back for the OBS cutover. All mutating ops are approval-gated — surface each for the human.
sha256 7a752bf0aafe8a47 — of the original file, so what was ingested stays checkable.
Plain — written for this website, not the source document
A running colony is being moved off one machine and onto a different appliance, and this dated plan frames the move itself as a live broadcast event.
It opens with the state at the time of writing. The old world is paused with its save intact, the stream is up showing a holding card, and one code fix travels with the colony.
Then come the facts about the destination machine, read off it rather than assumed, including that no colony container exists there yet and that every change that alters something waits on a human approval.
Two paths are described. The near one lifts the colony across as four containers, each named with its job, and notes that one piece is genuinely new on this machine because it needs headless graphics. The further one is a deeper convergence in which the colony becomes a world on the appliance's own runtime, and that is described as next rather than done.
The page ends with a prompt to hand to the agent doing the work.
Plain · written 2026-08-01 by claude-opus-5 · not yet checked by a person · about the document whose sha256 is 7a752bf0aafe8a47
Clear — written for this website, not the source document
A dated migration plan with a broadcast attached to it. The colony is being moved off one machine and onto a different appliance, and the move itself is being shown live.
The status block records the position at the time of writing. The old world is paused after a graceful stop with the save intact, and the stream is up showing a holding card over a status page. One code fix is already in the source and travels with the colony.
A facts section describes the destination, and it is careful to say these were read through a management interface rather than assumed. It gives the machine's memory and disk headroom and its load, notes that it runs containers with elevated privileges, and lists what is already running there. Two things then matter for the plan: no colony container is present, because the colony has never run there, and every operation that changes something waits on a human approval in the appliance's own queue. A note says where data should live and which location to avoid.
The near-term path is a lift-and-shift as four containers, each described by its job. First the game server, with a fixed world seed and remote console enabled. Then the colony itself, which serves a status page and reaches the game server, carries the fix, and keeps the standing rule that its inference has no foreign computation layers. Then a set of bodies, and a camera. The camera is singled out as the one genuinely new piece here, because it needs a graphics context with no screen attached. Deployment notes cover a shared network so the parts find each other by name, persistent service definitions, and opening a firewall on the local network so the existing broadcast machine can capture the two surfaces during the changeover. Verification is named: the colony ticking, the camera rendering, and the status page serving. Then the broadcast cuts back from the migration card to the live scene.
The further path is described as next rather than done: the colony becomes a world on the appliance's own inference runtime, with the streaming also happening there. It is labelled as the deeper convergence work.
The page ends with a prompt written to be handed to the agent performing the work. It restates the plan as instructions, names what to report back, and repeats that every changing operation is approval-gated and must be surfaced for a human.
Clear · written 2026-08-01 by claude-opus-5 · not yet checked by a person · about the document whose sha256 is 7a752bf0aafe8a47