Wiki · The Colony & the Method
RESUME — Producer expert build DONE; go-live after reboot (2026-07-11)
[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.
STATUS (2026-07-11 late): SUPERSEDED as the go-live path. Read STUDIO_SYSTEMS.md FIRST. The bring-up sequence below is System 1 (dev studio) and remains valid for the colony SOURCE; public broadcasting now goes through System 2 (
production/per P1-BRINGUP.md). The overlay proof gate (viewer\verify_overlays.cjs) is binding on any bring-up claim.
Read this first on resume. The Producer "expert show-host" build is complete, committed, and PUSHED (origin at
e310a76). This doc is the validated go-live sequence for after the reboot.
What is done (all committed + pushed, covenant-green)
The Producer is now a durable, deep, honest, self-running show-host. Commits c40c51b→e310a76
on lab/ozone-life-uni-hard-science:
- Durable —
SP.Show.Supervisor(lib/sp/show/) supervises Colony→Director→Producer→ OverlayPublisher (:rest_for_one). A Director crash restarts the Producer WITH it (re-asserts:producer) — the puppet-cam state is structurally impossible./producer/healthreports LIVE/PARTIAL/DOWN. - Sees deep + world — viability body (energy/gut/soma/fatigue) + phase + focus on the cards;
SP.Producer.WorldSensornarrates day/night + colony size over RCON (Markov-safe, no coords). - Story + honesty — four distinct beats (crisis/social/mind/recap via
SP.Brain.Narrator); per-UNI phase-climb + survival arcs;SP.Brain.Fenceon EVERY on-air path (narration + Q&A); in-app supervisedSP.Show.OverlayPublisher(the hand-launchedbroadcast_bridge.exsis retired). - Covenant at every step: gates 14/17/18 PASS, brain suite 334/0, motor posterior 0.75, byte-identity mad<1e-12. All narration pure-Elixir/5-language; FE decision math untouched.
GO-LIVE sequence (after the reboot)
ONE node only. The show auto-starts supervised with the node (UNI_AUTOSTART=1).
# 1) full studio bring-up (Minecraft -> supervised Phoenix show -> camera -> OBS -> studio).
# studio_up.ps1 launches Phoenix with UNI_AUTOSTART=1 (supervised show + design colony) and a
# puppet-cam guard that reads /producer/health.
powershell -File viewer\studio_up.ps1
# 2) confirm the REAL Producer is running the show (not the headless puppet):
Invoke-RestMethod http://localhost:4000/producer/health # want: verdict=LIVE, driver=producer, colony_count>0
# also open http://localhost:4000/stream — camera + narration + per-agent cards + Q&A
# 3) (optional) design colony override: set UNI_KIN before studio_up, e.g. $env:UNI_KIN='0,1,1,2,3'
# (default). Forest seed / world is the mcserver world.
# 4) to STREAM to YouTube/Twitch (the OBS path): keys + restream.ps1 + command center GO LIVE
# (unchanged; see docs/RUNBOOK_STUDIO.md + docs/STUDIO_OPERATOR_MANUAL.md).
# 5) full stop (kills EVERYTHING, verified clean):
powershell -File viewer\studio_up.ps1 -Stop
Puppet-cam guard (the recurring failure, now impossible)
If you ever see the camera orbiting with no narration / "Director moved too quickly", the Producer
is not running. With this build that can't persist: the supervisor restarts it, and
/producer/health will show verdict != LIVE. studio_up.ps1 warns on bring-up if the camera is up
without a live Producer. NEVER run a second --sname uni node (studio_up guards against it) and
NEVER run director.js standalone.
Validation receipts (pre-reboot, this session)
See the commit chain + the session log. A live bring-up on the dev-box MC confirmed the supervised Producer drives the real camera, narrates real UNIs, /producer/health=LIVE, and the OverlayPublisher writes broadcast.json — then torn down clean for the reboot.
Coordination
The rung-1 (brain/body) agent runs a SEPARATE track (lib/sp/brain homeostat RED, default genome
byte-identical, gated :homeostat lineage in lab containers @[redacted: private-address] — NOT the dev-box
stream MC). felt_* field names confirmed unchanged. See memory/feedback_agent_coordination.md.
Before reboot: confirm the rung-1 agent committed + pushed its RED work.
sha256 f82f0feebc5704d2 — of the original file, so what was ingested stays checkable.
Plain — written for this website, not the source document
A dated handover note whose very first line says it has been superseded as the route to going live. A newer document is named to read instead. The bring-up sequence it contains remains valid for one part of the system.
What it records is a completed build. A show-hosting component was made durable by putting it under a supervisor, so that if the part that drives the camera restarts, the part that directs it restarts with it. That arrangement is described as making one recurring failure structurally impossible.
The rest is a numbered sequence for starting everything after a restart, checking that the real component is running rather than an unattended camera, optionally overriding the design colony it launches with, and stopping everything cleanly.
A section on that recurring failure is the useful part: what you would see if it happened, why it can no longer persist, and two things never to run.
Plain · written 2026-08-01 by claude-opus-5 · not yet checked by a person · about the document whose sha256 is f82f0feebc5704d2
Clear — written for this website, not the source document
A dated resume note for a single session's work, carrying a superseded banner at the top. It is no longer the route to going live, and a newer document is named to be read first. The banner is careful, though: the bring-up sequence below is still valid for one part of the system, while public broadcasting now goes another way.
The first section records what was completed and pushed. A show-hosting component was made durable by putting a chain of parts under one supervisor in an order that means a failure restarts everything downstream of it. The consequence is stated as the point. If the part that drives the camera crashes, the part that directs it comes back with it and reasserts its role. The failure where a camera runs with nobody directing becomes structurally impossible rather than merely unlikely. A health endpoint reports one of three states.
Further bullets describe what the component can now see, including a body-state view and a narrated sense of the world read over a remote console in a way that respects the boundary and carries no coordinates. Others describe the storytelling beats, per-agent arcs, a check on wording applied on every path that reaches the air, and a publishing component brought under supervision so a hand-launched script could be retired. A closing line records that the covenant held at every step, with the gates passing and the standard configuration unchanged.
The go-live sequence is then a numbered block of commands. Bring the studio up. Check that the real component is running rather than an unattended camera, by reading the health endpoint and opening the stream page. Optionally override the design colony's population. And finally the command that stops everything and verifies it is clean.
The section on the recurring failure is the most useful part of the page. It describes exactly what an operator would see if the camera were orbiting without a director, and explains why that state can no longer persist under the new supervision. Two things are named as never to do: never run a second node with the same name, and never run the camera script on its own.
A short validation paragraph records what a live bring-up showed before the restart, and a coordination note says which separate track was running elsewhere and what to confirm before restarting.
Clear · written 2026-08-01 by claude-opus-5 · not yet checked by a person · about the document whose sha256 is f82f0feebc5704d2