Wiki · The Colony & the Method
UNI Public Reproducibility Bundle
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: the manifest for the immutable public tag (public-<date>) that a stranger can pull to reproduce any of our gate verdicts.
Manifest schema: production/schemas/public_manifest.schema.json v1.
Consumer: uni-public-mcp.get_public_manifest() (production/mcp/SPEC_uni_public_mcp.md).
What is in the bundle
Every artifact needed to reproduce any of our verdicts from the seed alone:
Schemas (
production/schemas/*.schema.json).sensorium_envelope.schema.json— the row shape every OS spool wears.envelope.schema.json— the MCP response wrapper.gate_row.schema.json— the gate ledger row shape.evidence_bundle.schema.json— the approval bundle shape.public_manifest.schema.json— this manifest's own schema.claim_fence.json— the unified fence tokens.
Persona docs (
docs/lab_team/*.md).01_math_breaker.mdthrough05_embodiment_designer.md+README.md.- The auditable personas of the ship-gate review.
Gate log (
docs/gates/PUBLIC_GATE_LOG.md).- Every gate + verdict + receipt path.
Evidence-log frame schema (
docs/observability/evidence_log.md).- The per-tick blanket log shape (
{tick, world, body, genome, afferent, efferent, blanket}). - The four-check verifier (
SP.Sim.Verifier.check_log/1).
- The per-tick blanket log shape (
Charter (
CLAUDE.md:16-21).- Our binding statement of intent, verbatim.
PUBLIC_README (
docs/PUBLIC_README.md).- The human-language entry point.
This document (
docs/PUBLIC_REPRODUCIBILITY_BUNDLE.md).
How to reproduce a verdict
- Pull the public tag:
git clone -b public-<date> <origin> uni-public - Read
docs/gates/PUBLIC_GATE_LOG.md. Pick a gate you want to reproduce. - Open its
receipt_path. Note:- The code sha the run was executed at.
- The seed.
- The PASS + FALSIFIES conditions (pre-registered).
- Check out that code sha:
git checkout <sha>. - Run the RED launcher named in the receipt:
mix run runs/<launcher>.exs -- --seed <s>. - Compare your outcome to the PASS + FALSIFIES conditions.
If your outcome does NOT match, we owe you a correction. That is the invariant.
What is NOT in the bundle (deliberately)
- The stream keys. They live in
/etc/uni/runtime.envon node2 and are never in git. - The kin
.binmemory files. Those are per-lineage and per-seed; the reproducibility path starts from a seed, not a memory. - Real-time operator state. This is a frozen public tag, not a live subscribe.
Immutability
Once a public tag is minted, the artifacts under it are immutable. If we find an error in a receipt, we mint a NEW dated tag with a corrected receipt AND a CORRECTION_NOTE.md naming the changed row + reason. The old tag stays.
How to verify the bundle itself
The manifest at production/schemas/public_manifest.schema.json shape names every file in this bundle with its sha256. To verify:
sha256sum -c production/schemas/public_manifest.sha256
If any sha differs, the tag has been tampered with. Do not trust it.
Reporting a falsification
If you cannot reproduce a verdict, or you find an over-claim, or you discover a gate whose FALSIFIES condition was met but marked PASS:
- Open an issue on the repo (public branch).
- Or send us the diff of your reproduction attempt.
- We publish corrections as new dated public tags with a
CORRECTION_NOTE.md.
This is not just a slogan. Falsifications are how UNI improves.
Cross-references
docs/PUBLIC_README.md— the stranger's entry.docs/gates/PUBLIC_GATE_LOG.md— the human-rendered gate log.production/mcp/SPEC_uni_public_mcp.md— the read-only MCP surface.production/mcp/SPEC_colony_transcript_replay.md— the transcript replay surface.
sha256 c0b42154a04733e7 — of the original file, so what was ingested stays checkable.
Plain — written for this website, not the source document
This page is a manifest. It lists what a stranger gets when they pull a frozen public tag, so they can reproduce any of the project's verdicts from a seed.
The list is short and specific. The schemas that define the shapes of things, the reviewer persona documents, and the gate log with its records of what was run. The shape of the per-tick evidence frames, the binding charter, the public introduction, and this page itself.
A numbered procedure explains how to reproduce a verdict, and the page states the invariant plainly: if your outcome does not match, they owe you a correction.
Just as useful is the section on what is deliberately not in the bundle. Stream keys, which live outside the repository. Per-lineage memory files, because the path starts from a seed rather than from a memory. And live operator state, because this is a frozen tag rather than a subscription.
Tags are immutable. A correction becomes a new dated tag with a note naming what changed.
Plain · written 2026-08-01 by claude-opus-5 · not yet checked by a person · about the document whose sha256 is c0b42154a04733e7
Clear — written for this website, not the source document
This is a manifest for a public, frozen tag: the set of artifacts a stranger can pull in order to reproduce any of the project's gate verdicts starting from a seed. It names its own schema and the read-only interface that serves it.
The contents are enumerated in seven groups. The schemas that fix the shape of a data row, a response wrapper, a row in the gate list, an approval bundle, the manifest itself, and the list of words a claim may not use. The reviewer persona documents that make the ship-gate review auditable. The gate log with every verdict, and the path to each file recording what was run. The schema of the per-tick evidence frame together with the checks its verifier runs. The binding charter, quoted verbatim. The public introduction written for a person rather than a machine. And this document.
A numbered procedure follows for reproducing a verdict. Clone the dated tag, read the gate log, pick a gate, and open its receipt — the file recording what was run. Note the code point, the seed and the conditions registered in advance, check out that code point, run the named launcher with the same seed, and compare. The page then states the invariant in one line: if your outcome does not match, the project owes you a correction.
The section on what is deliberately absent is as informative as the contents. Stream keys are not there and live outside the repository. Per-lineage memory files are not there, because the reproducibility path starts from a seed rather than from a saved mind. And live operator state is not there, because this is a frozen tag rather than a live feed.
Immutability is then declared. Once a tag is minted its artifacts do not change. An error in a receipt is handled by minting a new dated tag carrying a corrected receipt and a note naming the changed row and the reason, and the old tag stays where it is.
A short section explains how to check the bundle itself: the manifest names every file with its digest, and a single command re-checks them. If a digest differs, the page says the tag has been tampered with and should not be trusted.
The final sections explain how to report a falsification, whether that is a verdict you cannot reproduce, an over-claim, or a gate whose refuting condition was met but recorded as a pass. The page says corrections are published as new dated tags, and that this is not a slogan.
Clear · written 2026-08-01 by claude-opus-5 · not yet checked by a person · about the document whose sha256 is c0b42154a04733e7