Wiki · The Colony & the Method
PROJECT STATUS — shared tracker (all agents read this first)
[redacted: category] — 4 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.
⚠️ ARCHITECTURE CORRECTION (2026-07-12, owner-set): the "System 2 on uni-lab-79740c" framing below is STALE. Render/mixer/encode = native Windows OBS on THINKER (portable, any GPU box); node2 = relay ONLY; the COLONY runs on UNI-LAB (
[redacted: private-address]), rootless, on the chip — ALWAYS, captured by THINKER over the LAN. Canonical:CLAUDE.md, ADR-PROD-013,docs/UNIVERSE.md.Status update (2026-07-11 late). Studio/platform state is now owned by
docs/STUDIO_SYSTEMS.md+production/docs/DEPLOYED_STATE.md(System 2 P1 core DEPLOYED + PROVEN on uni-lab-79740c; not WIP). The colony source is DOWN for the emergent-forage rebuild.
Canonical cross-agent status. Updated 2026-07-11 ~10:30 (post-reboot audit). Branch
lab/ozone-life-uni-hard-science, HEAD pushed toorigin(github TMDLRG/UNI.MineCraft). The live master-plan page (http://[redacted: private-address]:4100/— index.html/plan.md/state.json) is generated from this repo; where they disagree, this file + the committed receipts win. Rules that bind every agent: one cure at a time · pre-registered gates · receipts beat rhetoric · claim fence (behaviour only, never experience) · live-stream guard (owner go-ahead before any new lineage on the streamed colony).
OWNER DIRECTIVE (current, 2026-07-11)
- Prove the next gate (rung-1 graded-viability paired RED) — do not weaken bars.
- Producer + stream up together: run the full show ~1 hour WITHOUT remote stream keys (local-only: OBS → MediaMTX, no YouTube/Twitch push) as a stability soak.
- If stable → flip live (attach the remote keys / start the platform push) and keep working through gates while live.
Post-reboot audit (2026-07-11 10:29, RE-VALIDATED 10:40 — all green)
Box up since 10:07:11 (no further reboot as of 10:40). Re-ran the full audit: identical GREEN result below.
- Dev box rebooted 10:07:11. Repo clean at
d6ead4b+;mix test test/sp/brain/= 315/0 (byte-identity mad<1e-12, action-clone, motor posterior 0.75 unchanged); offline gates GREEN (verify_v2_isolation8/8 ·verify_rung1_step15/5 ·verify_rung1_dynamics4/4 VIABLE). - Local stack (post-reboot bring-up 10:14): Minecraft :25565 UP · ONE Phoenix
-sname uninode UP (/streamHTTP 200 — the erl.exe pair is launcher+child, NOT a duplicate; the-Statusguard over-counts iex.bat) · MediaMTX :9997 UP · command center :8098 / overlay :8099 / publisher :8443 UP · OBS down · colony cam :3020 down — colony not yet populated (dev box needs the deliberate trigger; see studio handoff). - Lab box (
uni@[redacted: private-address]): onlymc-server(healthy); gate worlds torn down; master-plan page HTTP 200. - Secrets guard: root
auto.crt/auto.key(EC private key) now gitignored — never commit.
Track A — brain/body (Stratified Palimpsest engine) — owner: the brain/body agent
| item | status | receipt |
|---|---|---|
| Metabolism activation gate (organ live + death edge, pos/neg/neg/pos) | PASS WITHDRAWN: the PASS rested on an RCON food-give now judged a fake-life hack (see docs/receipts/metabolism_activation_gate_LIVE.md); mechanism-when-driven holds, survival claim withdrawn; emergent-forage rebuild in commit f0c789a, pending a colony survival gate |
docs/receipts/metabolism_activation_gate_LIVE.md |
| Regulation gate v1 (setpoint vs saturable) | FALSIFIES (verified) | docs/receipts/metabolism_regulation_gate.md |
| Regulation gate v2 (confound-free, N=12) | FALSIFIES (verified; flat setpoint dies 6/12, looser dispersion) | docs/receipts/metabolism_regulation_gate_v2.md |
| Full-depth model design (owner depth correction) | SIGN-WITH-CHANGES | docs/specs/generative_model_depth.md |
| Rung-1 engine (cures 1+2+3): graded per-subsystem viability + work/fatigue | BUILT + offline-proven (315/0; dynamics 4/4: survives where flat setpoint died, interior reserve, paces, dissociates) | docs/specs/rung1_graded_viability.md, lib/sp/brain/homeostat.ex, commits 1c49e62..784eabd |
| Rung-1 paired RED — control-arm FE (setpoint6/saturable6/ablation/severed arms) | BUILT + lab-team SIGN-WITH-CHANGES + committed 41abd65 (pushed). 5-persona review caught a real pre-reg bug (PASS-4 backwards → split); default byte-identical, suite 334/0, +19 invariant tests, A6 controls 3/3 |
docs/receipts/rung1_graded_viability_RED.md (pre-reg + REVISION 1 verdict), docs/specs/rung1_graded_viability.md (REVISION 1 spec + ship-gate checklist) |
| Rung-1 paired RED — LIVE burn (the next gate to prove) | READY — pending owner go-ahead + live-stream guard (post-reboot: lib/harness sync to lab box → gate containers kin 60 → live smoke on FULL → N=12 → runs/analyze_rung1_red.py). Harness runs/rung1_red.exs + analyzer committed |
docs/receipts/rung1_graded_viability_RED.md |
Default colony genome is byte-identical throughout — nothing currently streamed changed; the :homeostat
depth is a gated lineage that only appears in the RED.
Track B — broadcast studio / Producer — owner: the studio agent
| item | status | receipt |
|---|---|---|
| Studio Phase-1 hardening + verified -Stop + zombie guards | DONE | commits a9ea510, 0a88943 |
| Headless-director incident (puppet cam) | killed + documented; never run director.js headless |
docs/RESUME_RUNG1.md open-issue block, docs/RESUME_2026-07-11_STUDIO.md |
| Real Producer restore path | stack up post-reboot; finish = populate colony (elixir --sname trig --cookie [redacted: credential] runs\trigger.exs), Producer then drives the Director in :producer mode |
docs/handoffs/BROADCAST_STUDIO_HANDOFF.md (read this) |
| Known gap | studio_up.ps1 does not start/verify the Producer or colony — add a step or warn loudly |
studio resume §1 |
| Phase-2 service-based platform (replace the cmd-window fleet) | WIP committed for continuity (production/, docs/UNI_PRODUCTION_PLATFORM.md) |
studio resume §2 |
The keyless stability soak → flip-live plan (the directive, operationalized)
- Studio agent: populate colony (
runs\trigger.exs) → confirm Producer cutting shots on/stream, colony cam :3020 up, OBS up (crash-dialog gotcha), stream to MediaMTX only (no remote keys). - Soak ≥60 min: watch
studio_up.ps1 -Status(no zombies/dupes), MediaMTXunipath ready, no process restarts (watchdog log), Producer still directing (shots changing), colony alive. - Brain/body agent (in parallel): pre-register the rung-1 RED (
docs/receipts/rung1_graded_viability_RED.md), sync lib to the lab box, ready the N-world harness — so gate-proving continues during/after the soak. - Stable ⇒ owner flips live (remote keys attached) → keep working gates one cure at a time.
Honesty fence for anything on-stream (binding)
The Producer UNI directs the broadcast (a real active-inference show-runner, a production role); it is never
narrated as a colony UNI choosing its own view. Raw UNI POV = the per-UNI :camera_control/body.js feed, a
separate labeled channel. No gate result is captioned beyond its recorded verdict (PASS/PARTIAL/FAIL/WITHHELD);
graded interoceptive signals are model variables, never "felt". 4-value fence on every claim
(proven/designed/hypothesized/not-yet-built).
Read-first map
- This file →
docs/RESUME_RUNG1.md(brain/body deep state) ·docs/handoffs/BROADCAST_STUDIO_HANDOFF.md+docs/RESUME_2026-07-11_STUDIO.md(studio) ·docs/LAB_PROTOCOL.md(rules) ·docs/DEEPENING_PLAN.md(plan) · master-plan pagehttp://[redacted: private-address]:4100/.
sha256 0caf29aa4451f275 — of the original file, so what was ingested stays checkable.
Plain — written for this website, not the source document
The first thing on this shared status tracker is a correction, not a summary. A framing used further down the page is marked stale by the owner, with the corrected picture given in the same breath and the documents that override them named.
It then carries the current directive in three numbered steps, an audit taken after a restart, and two tables, one per track of work, each row giving an item, a status, and the record of what was run behind it.
The statuses are what make it worth reading. One row records a pass that was withdrawn, because it rested on something later judged a shortcut, with the mechanism claim kept and the survival claim dropped. Two rows record outright refutations. Several are waiting on the owner's go-ahead.
A binding honesty rule closes it: internal signals are model variables and are never described as felt, and no result is captioned beyond its recorded verdict.
Plain · written 2026-08-01 by claude-opus-5 · not yet checked by a person · about the document whose sha256 is 0caf29aa4451f275
Clear — written for this website, not the source document
Anyone joining the work is asked to read this cross-agent tracker before anything else, and it is written for that.
It opens with a correction rather than a summary. A framing used elsewhere on the page about which machine does what is marked stale by the owner, and the corrected arrangement is stated immediately, with the documents that hold the version that counts named. A second note reassigns ownership of the studio state to other documents and records that one source is deliberately down for a rebuild. A third block establishes precedence: a live page is generated from this repository, and where they disagree, this file and the committed receipts — the files recording what was run — win. The binding rules for every agent are then restated in one line. One cure at a time, gates registered in advance, and receipts over rhetoric. A stated limit keeping claims to behaviour rather than experience, and a guard requiring the owner's go-ahead before anything new runs on the streamed colony.
The owner's current directive is three numbered items. Prove the next gate without weakening its bars. Run the whole show for about an hour with no remote keys as a stability soak. And if that is stable, go live and keep working through gates while live.
An audit taken after a restart follows, and it is careful about what it actually checked. It records the test suite passing, offline gates green, and which local services came up and which did not. One apparent duplicate process is actually a launcher and its child rather than a real duplicate, and the colony is not yet populated. A key file has been excluded from version control, with an instruction never to commit it.
Two tables then cover the two tracks. The first, for the engine and body, contains the most instructive rows. One records a pass that was withdrawn, because it rested on food handed to the agents which was later judged a shortcut; the mechanism claim is kept and the survival claim withdrawn, with a rebuild pending its own gate. Two rows record outright refutations of a regulation gate, one of them confound-free at a larger sample. Another records an engine built and proven offline. Another records a paired experiment built and reviewed, where a five-persona review caught a real error in the conditions written down beforehand. The last is ready and waiting on the owner's go-ahead. A line beneath notes the default configuration is unchanged throughout, so nothing being streamed has moved.
The second table covers the broadcast studio. It includes a hardening pass, and an incident with a camera running without its driver, which is recorded as killed and documented. It includes a restore path, a known gap where a bring-up script does not start or check one component, and a platform rebuild in progress.
A numbered plan operationalises the directive, and a binding honesty limit closes the page. The directing component is a production role and is never narrated as a colony member choosing its own view. No result is captioned beyond its recorded verdict, internal signals are model variables and never described as felt, and every claim carries a four-value label limiting what may be said.
Clear · written 2026-08-01 by claude-opus-5 · not yet checked by a person · about the document whose sha256 is 0caf29aa4451f275