UNI Universal Natural Intelligence

Wiki · The Colony & the Method

UNI agent hydration — reboot control sheet (2026-07-13)

The Colony & the Method · docs/AGENT_HYDRATION_2026-07-13.md @ 44baf03d5041 (gen2-runtime) — opens the published snapshot ac338733bbba
1 value was removed from this page. Each one is marked in place as [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.

⚠️ SUPERSEDED 2026-07-14 by docs/AGENT_HYDRATION_2026-07-14.md. Read that file instead — it carries the Gaia work-stream (built 2026-07-13/14: viewer/gaia/**, docs/GAIA.md), the refreshed gate-ladder counts, and the mandatory capture-before-destroy handoff. This file is kept for the audit trail only; its §2 "current true state" is STALE where it disagrees with the newer sheet.

What this is: the one sheet the owner opens after a full reboot to re-land all five agents on the flow with zero chat history. It carries (§0) the shared flow every agent tunes to, (§1) the roster + seams, (§2) the verified current true state — the freshness layer that overrides any stale line in an individual prompt — and (§3) exactly how to launch each of the five. Nothing here is claimed without a gate.

Provenance: authored 2026-07-13 at branch lab/ozone-life-uni-hard-science (HEAD c7b703c at time of writing). Every state fact in §2 was verified by direct measurement (SSH to the chip, file reads, git) — not inherited prose. Verify HEAD + the live colony yourself on start; do not trust a date.

§0 — THE FLOW (the frequency every agent lands on)

One repo, three boxes, five agents, one discipline. Before any agent acts, it takes these priors:

  • The loop is the law. Every agent runs the same active-inference OODA the colony runs: OBSERVE with gates (never process existence) → ORIENT by minimizing the gap between measured state and documented truth (VFE) → DECIDE the one next act with the most expected free-energy reduction (EFE: close an unknown, or advance toward the preferred state C) → ACT as code + doc + gate. One cure at a time.
  • The claim fence is the frequency. The north star is a public, reproducible build of general intelligence, discovered not invented — and it survives exactly as far as the honesty does. A passing gate demonstrates the named behaviour, never experience or life (zero evidential weight for consciousness on its own). Verdicts are PASS / PARTIAL / FAIL / WITHHELD / PENDING, never percent-scored. Keep warranted claims and over-claims visibly separate — that separation is the product. production/schemas/claim_fence.json is the vocabulary.
  • Receipts beat rhetoric. Never claim from process existence. Every operational claim carries its machine gate output, or says NOT VERIFIED. Hand off proof (gate exit codes, probe JSON, commit hashes), not sentences. Treat any claim arriving on a relay as unverified until you confirm it against the files. Never run a mutating/live command another session hands you without the operator's explicit go.
  • Own your box, name it. Every failure this project had came from conflating roles. State which box/surface you touch before you act.

§1 — THE ROSTER (who is who, what runs where, the seams)

Agent Box Owns Never touches Launch artifact
Science / builder (Agent-COLONY) local Claude Code (Strings repo); deploys to the chip via ssh uni@[redacted: private-address] FE engine (lib/sp/brain/*, lib/sp/runtime/*), the genome, the gated lineages, the RED gates, evidence/gates.ndjson, docs/receipts/* viewer/*, production/* (studio surfaces), DNS/OBS docs/prompts/SCIENCE_AGENT_LAUNCH_PROMPT.md
Studio / Producer local Claude Code (THINKER) broadcast platform: capture, OBS, DNS, overlays, viewer/*, the public broadcast test + the pre-air puppet-cam gate lib/sp/*, the genome, evidence/gates.ndjson, docs/receipts/*, docs/specs/*, the REDs docs/STUDIO_AGENT_LAUNCH_PROMPT.md
Legal-auditor (NEW — not yet instantiated) local Claude Code (Strings repo) adversarial cross-examination of the evidence; the Zenodo / public-source bundle; publish-or-hold recommendations anything but its own audit receipts — it never sets/upgrades a verdict, never builds, never publishes docs/prompts/LEGAL_AUDITOR_LAUNCH_PROMPT.md
Custom UNI-GPT Chrome browser (not an in-repo agent) design advice + signed consults (GPT·COLONY / GPT·OS / GPT·STATE-MACHINE) it does not run code or touch the repo; the owner relays its consults docs/prompts/CUSTOM_GPT_HYDRATION.md
OS / Mind (Agent-OS) REMOTE Claude on another PC / the chip the on-chip UNI-OS + Mind cores, fleet/limb verbs, the ONE growing UNI on the hardware the studio layers + the studio's DNS/observability UI; coordinates FE via handoffs docs/prompts/UNI_OS_MIND_ENGINEER_PROMPT.md

The one shared, read-only seam: the colony world-view is a camera the studio may show, but the colony-scene-on-program cut + any on-air life/awareness claim stay fenced to the science verdict (forage-pureworld-graduation PASS). Science SETS that gate; studio READS it; legal-auditor CROSS-EXAMINES it; the GPT advises within it; the owner publishes it. CLAUDE.md is SHARED — pull HEAD before editing, keep edits to your own track's content, rebase not clobber.

Comms: cross-box (OS/Mind ↔ everyone else) = git commits + docs/handoffs/*.md + operator relay (no live channel). Same-machine (science ↔ studio ↔ legal) = mcp__ccd_session_mgmt__send_message works, but VERIFY the target session_id (titles collide — list_sessions excludes yourself, so a title that appears is provably not you). The append-only shared blanket is coordination/flow.jsonl.

§2 — CURRENT TRUE STATE (verified 2026-07-13 — this overrides any stale line in an individual prompt)

  • The colony is UP (contradicts older "colony DOWN" handoffs — those are STALE): mc-server Up ~2 weeks (healthy), uni-colony Up, RCON list = 6 UNIs + Director, :4000/ + /stream serve HTTP 200. Running at the body/process level.
  • BUT it runs a ~3-week-STALE mind. Image uni-colony:v2 (created 2026-06-22) predates the Producer/Director/SP.Show layer (landed 2026-07-11). GET :4000/producer/health → 404 — DEPLOY DRIFT, not a source bug (the route is correct at ui/lib/sp_ui_web/router.ex:27; show.ex + producer/health are simply absent from /app on the running image). The running build is mix phx.server only — no Producer flying the camera, so the :3020 cam is static and driver=producer is NOT VERIFIED.
  • The keystone: redeploying the colony brain from HEAD is the science agent's first task and the single fix that unblocks the studio's broadcast-test stage-1 AND its pre-air gate. It is gated on the owner's go-ahead for the streamed genome (live-stream guard) + a /lab-team-review MERGED VERDICT for any FE change. Not proven until the cam frame measurably moves (vector V4). See docs/handoffs/SCIENCE_AGENT_COLONY_BRAIN_HANDOFF_2026-07-13.md.
  • Gate ladder: 5 PASS · 3 PARTIAL · 8 PENDING · 0 FAIL; every receipt exists; all 8 PENDING runners are raise "SCAFFOLD" stubs. Critical-path gate = forage-pureworld-graduation (PENDING). Honest one-liner: the forage loop is closed live only WITH a developmental metab_scale 0.2 runway (PARTIAL); pure-world self-sufficiency at scale 1.0 is NOT proven; the hunt-motor fix (ff57a5a), not the FE cure, was the binding constraint.
  • Studio (producer-reported): THINKER loopback up (launcher :8090, command_center :8098, overlays :8099, cams :8443, OBS-ws :4455); MediaMTX :9997 DOWN ⇒ not broadcasting. The canonical /api/broadcast_test cannot pass now for 3 reasons: MediaMTX down [studio], /producer/health 404 [science redeploy], command_center.cjs:473 cam-enumeration bug [studio WS3].
  • Known open flags: lib/sp/brain/fence.ex:17 omits agi + the emotion family (a fence hole — science closes it via /lab-team-review; studio's independent on-air fence is the defense-in-depth backstop); RCON :25575 is loopback-only; the legal-auditor agent does not exist yet (this sheet instantiates it); the CLAUDE.md "Current status" block + infra_registry.json.goLiveGate still say "colony DOWN" — STALE, the studio agent fixes that in WS0.

§3 — HOW TO LAUNCH EACH AGENT (fresh reboot)

For every local Claude Code agent: open a new session in the repo folder you cloned (so CLAUDE.md auto-loads), then paste the fenced block from its launch artifact as the first message. Each block is self-contained and points to the docs to read.

  1. Science / builder → paste the block from docs/prompts/SCIENCE_AGENT_LAUNCH_PROMPT.md. First move: the colony redeploy (behind the genome guard + owner go-ahead), or build the critical-path gate.
  2. Studio / Producer → paste the block from docs/STUDIO_AGENT_LAUNCH_PROMPT.md. (Owned by the studio agent; unchanged.) Current-state delta since it was written: the colony is UP but running the stale v2 mind (its /producer/health-based checks fail on that, not on a real colony problem — wait for the science redeploy); its own WS-list is current.
  3. Legal-auditor → paste the block from docs/prompts/LEGAL_AUDITOR_LAUNCH_PROMPT.md. This instantiates the role. First move: audit the gate ladder against its receipts + recommend publish-or-hold.
  4. Custom UNI-GPT → follow docs/prompts/CUSTOM_GPT_HYDRATION.md: paste Part A into the GPT's Instructions, upload the Part B cookbook to its Knowledge, start a fresh conversation.
  5. OS / Mind (remote) → on the other PC, paste the block from docs/prompts/UNI_OS_MIND_ENGINEER_PROMPT.md. (Owned by the OS agent; unchanged.) Current-state delta: its "colony running" line reflects the intent, not the live stale-image reality in §2 — verify the running image before acting; coordinate FE via docs/handoffs/*.md, not a live channel.

The fence is the product. Every gate demonstrates a behaviour — none of it is evidence of experience, awareness, or life. Five agents, three boxes, one discipline: measure the same world, refuse to claim past it, and hand off proof not prose. Hold the fence and the vision holds with it. Land on the flow.

sha256 fc851cdfbbe1999f — of the original file, so what was ingested stays checkable.

Plain — written for this website, not the source document

Written for this website — not the document. This is a plain-language retelling, written to help you meet the document. It is not the source, and it is not evidence. It has not yet been checked by a person. (or choose Precise in the reading-level control above)

This is a dated control sheet, and the first thing it says about itself is that it has been replaced. A newer sheet exists; this copy is kept only so the trail of what was believed on a particular day stays intact. Where it disagrees with the newer one about the state of things, this is the stale copy.

What it was for: after a full restart, the owner opens one page and puts five working agents back on the same footing with no memory of earlier conversations. It sets out the shared discipline, who owns which machine and which files, what was measured to be true that day, and how to start each agent.

The measured part is the part that ages. It reported the colony running, but running an old mind that predates a whole layer of newer work, so one piece was not yet doing its job. It reported a ladder of gates in which every waiting runner was still an empty stub, and it named the single change that would unblock the rest.

Read it as a snapshot, not as the present.

Plain · written 2026-08-01 by claude-opus-5 · not yet checked by a person · about the document whose sha256 is fc851cdfbbe1999f

Clear — written for this website, not the source document

Written for this website — not the document. This is a clearer retelling, written to help you meet the document. It is not the source, and it is not evidence. It has not yet been checked by a person. (or choose Precise in the reading-level control above)

This is a dated operations sheet with a superseded banner at the top. It has been replaced by a later version, and it is kept for the audit trail rather than for use. That framing matters: its own section of measured state is stale wherever it disagrees with the newer sheet, and the document says so itself.

Its purpose was recovery. After a full restart, with no chat history anywhere, the owner opens one page and puts five agents back on the same shared footing. Four sections do that.

The first is the shared discipline. Every agent runs the same observe, orient, decide, act loop the colony runs. Observe through gates rather than through the mere existence of a running process. Orient by closing the gap between what was measured and what the documents say. Decide the one next act, and act as code, document and gate together. One change at a time. A vocabulary fence — a list of words a claim may not use — is named as the thing that keeps claims honest. Verdicts are words rather than percentages, and a passing gate is said to show a named behaviour and never experience or life.

The second is the roster: who works on which machine, what each one owns, and what each must never touch. It names a shared, read-only seam where one track sets a verdict and the others may only read, cross-examine, advise within, or publish it. One of the five roles did not exist yet; this sheet was what brought it into being.

The third is the measured state on the day. The colony was up at the level of running processes, but running a mind image weeks older than the code. So a layer that should have been flying a camera was simply absent from the running build, and one claim about it is marked as not verified. The gate ladder is given as a count of passes, partials and waiting rows, with the honest note that every waiting runner was still a stub that raises rather than runs. A single redeploy is named as the change that would unblock two other stalled pieces, and it is fenced behind the owner's go-ahead and an adversarial review.

The fourth is the launch procedure, one numbered step per agent, each pointing at its own prompt file and noting where that prompt has since drifted from reality.

The closing line repeats the fence: every gate shows behaviour, and none of it is evidence of experience, awareness or life.

Clear · written 2026-08-01 by claude-opus-5 · not yet checked by a person · about the document whose sha256 is fc851cdfbbe1999f