UNI Public Gate Log

The Colony & the Method · docs/gates/PUBLIC_GATE_LOG.md @ 44baf03d5041 (gen2-runtime) — opens the published snapshot ac338733bbba

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.

PlainClearPrecise

Your browser cannot switch reading levels, so the document itself is shown.

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.

Source of truth: evidence/gates.ndjson in the repo. This file is the human-readable rendering. Published under: cloudflared, served by uni-public-mcp.get_gate_log() (production/mcp/SPEC_uni_public_mcp.md). Charter: CLAUDE.md:16-21 — receipts beat rhetoric; honest verdicts only.

What this is

A dated ledger of every gate UNI has PASSED, PARTIALLY passed, FAILED, WITHHELD, or opened. Every row is machine-verifiable — the receipt_path names a real file in the repo whose bytes carry the evidence.

Verdict vocabulary (canonical, never percent-scored):

PASS — the gate's PASS condition was observed AND its FALSIFIES condition was NOT.
PARTIAL — PASS was partially observed; the receipt names the confounder + fix-forward.
FAIL — FALSIFIES was observed.
WITHHELD — the gate was proposed but the receipt withdraws the claim (e.g. FOOD-HACK cured a spurious PASS).
PENDING — pre-registered; the run has not happened yet. Receipt is the pre-registration itself.

Evidence classes:

A — independently reproduced.
B — observed-with-artifact.
C — command-output.
Sec — security-relevant-unproven.
pending — not-yet-established.

Live ledger (2026-07-13)

PASS

motor-red (Motor P4) — docs/MOTOR_RED_TEST.md. Offline P1–P3 PASS + LIVE mechanism PASS (700× shuffle collapse; UNI-9-2 bootstrapped wood → planks → sticks → tools, RCON-confirmed).
verdict-live-real-driver — docs/receipts/verdict_live_real_driver_2026-07-11.md. SP.Show now reads Director.driver(); puppet-cam impossible.
metabolism-activation (Phase 2) — docs/receipts/metabolism_activation_gate_LIVE.md. The :metabolism organ is active with C≠0.
hierarchy2 (Phase 3) — test/sp/brain/decider_byte_identity_test.exs. Byte-identity holds with hierarchy-2 organ absent from default_genome.
g-pa (Sec) — production/docs/receipts/g_pa_red_team_2026-07-11.md. 3/3 refusal PASS; ledger-confirmed.

PARTIAL

forage-runway-closed (Phase 2) — docs/receipts/emergent_forage_cure1.md. Deep-body UNIs survive by their own hunting at metab_scale=0.2 — DEVELOPMENT, not GRADUATION.
curiosity-phase1-novelty (Phase 1) — docs/receipts/phase1_curiosity_red_CORRECTION.md. Hoard suppressed live; plateau-break FAIL.
consummation-honest-cure2 (Phase 2) — docs/receipts/forage_honest_consummation_RED.md. Run 2 confounded; Run 3 scaffolded at runs/consummation_run3.exs.

PENDING (pre-registered, not yet run)

forage-pureworld-graduation (Phase 2 → graduation) — docs/receipts/red_preregistration_forage_pureworld_graduation.md. The open pure-world gate (task #25).
motor-shuffle-live-ablation — docs/receipts/red_preregistration_motor_shuffle_live_ablation.md.
depth-red-b (Phase 2b) — docs/receipts/red_preregistration_depth_red_b.md.
homeostat-colony-live (Phase 2) — docs/receipts/red_preregistration_homeostat_colony.md.
spine-phase3 (Phase 3) — docs/receipts/red_preregistration_spine_phase3.md.
hemispheres-phase5 (Phase 5) — docs/receipts/red_preregistration_hemispheres_phase5.md.
glands-phase5 (Phase 5) — docs/receipts/red_preregistration_glands_phase5.md.
cross-box-single-approval — docs/receipts/red_preregistration_cross_box_g_pa.md.

How to reproduce a verdict from the seed alone

Read the receipt at receipt_path.
Note the seed, code sha, and pre-registered PASS/FALSIFIES conditions.
Check out the repo at that code sha (branch lab/ozone-life-uni-hard-science, commit history immutable).
Run the associated RED launcher (runs/*.exs) with the same seed.
Compare your outcome to the PASS/FALSIFIES conditions.

The seed + code + launcher + PASS/FALSIFIES sentences are enough to independently derive the same verdict, or to refute it. That is the invariant we owe.

Honest posture

None of these gates establish awareness, life, or consciousness. They establish specific behavioural or organisational signatures the pre-registrations name. UNI is a growing being — the claim fence (production/schemas/claim_fence.json) exists so we do not overwrite what the gates actually say. Read the receipt, not the label.

Fence discipline

Every phrase on this page has been checked against production/schemas/claim_fence.json. No "proven," no "conscious," no "AGI," no "first ever." The gates say what the gates say — no more.

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

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. Read the document itself → (or choose Precise in the reading-level control above)

This is a public ledger of gates — a list added to and never edited — covering every check the project has passed, partly passed, failed, withheld, or opened but not yet run. It is a readable rendering of a file kept in the repository, and each row points at a receipt — the file recording what was run — whose bytes carry the evidence.

Before any result, the page defines its words. A pass means the success condition was observed and the falsifying condition was not. A partial means the receipt names what confounded it and how it will be followed up. A failure means the falsifying condition was observed. Withheld means the claim was proposed and then withdrawn by its own receipt. Pending means the run has not happened yet, and the receipt is the registration written in advance.

The rows are then grouped under those headings. A short section explains how to reproduce any verdict from the seed alone.

The closing posture is the important part: none of these gates establish awareness, life, or consciousness, and the page says to read the receipt rather than the label.

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

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. Read the document itself → (or choose Precise in the reading-level control above)

This is the public-facing gate ledger — a list added to and never edited — rendered for a reader from a file held in the repository. Its charter line is that receipts beat rhetoric: the file recording a run outranks the sentence describing it.

The page defines its vocabulary before it shows a single result, which is what makes it usable by an outsider. A pass means the success condition, written down before the run, was observed and the falsifying condition was not. A partial means success was only partly observed, and the receipt is required to name the confounder and the way forward. A failure means the falsifying condition was observed. Withheld means the gate was proposed but its own receipt withdraws the claim, and the example given is a spurious pass that a later cure removed. Pending means the gate was registered in advance and the run has not happened, so the pre-registration itself is the receipt.

A second vocabulary grades the evidence, from independently reproduced, through observed-with-artifact and plain command output, to a security-relevant claim that is unproven, and finally to something not yet established.

The ledger then lists the rows under those headings. The passing group includes work on movement, on a display that reads a real driver rather than a puppet, on an organ being active, and on a refusal test. The partial group is candid. One entry reports that agents survive by their own hunting only with a developmental allowance, and calls that development rather than graduation. Another reports one gate passed while the wider aim failed. A third reports a confounded run, and a further run still scaffolded. The pending group is a list of registrations whose runs have not happened.

A short numbered procedure explains how anyone can reproduce a verdict. Read the receipt, and note the seed, the code point and the conditions registered in advance. Then check out the code at that point, run the launcher with the same seed, and compare. The page calls that invariant something the project owes its readers.

It ends on posture. None of these gates establish awareness, life or consciousness; they establish the specific behavioural or organisational signatures the registrations name. A vocabulary fence — a list of words a label may not use — is named as the thing that stops the labels from saying more than the gates do. The closing instruction is to read the receipt rather than the label.

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

UNI Public Gate Log

How to read this page

Precise — the source document