Wiki · The Colony & the Method
Signal Catalog
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.
All signals are SP.Core.Signal structs (CloudEvents 1.0 core attributes):
specversion, id, type, source, subject, time, datacontenttype, data.
time is the logical world tick, never wall-clock. type must be a
dot-segmented reverse-DNS string (validated by regex).
Sensor signals are produced by SP.Body.Sensor and are coordinate-free and
material-ID-free by construction. The learner does NOT see these directly; it
sees their SP.Interface-channelised projection (see action_catalog
and the leakage report). The semantic payloads below are the engineering view.
Sensor signals
| type | source | emitted when | data keys |
|---|---|---|---|
sp.sense.interoception |
sensor:interoception |
always (seed organ) | energy, hydration, temperature, integrity, budget |
sp.sense.chemotactile |
sensor:chemotactile |
organ chemotactile mature |
attractant, solvent, irritation, texture, feedstock_feel |
sp.sense.proprioception |
sensor:proprioception |
organ proprioception |
appendages, senses, parts, stage |
sp.sense.plume |
sensor:plume |
organ plume |
nutrient_gradient, toxin_gradient, nutrient_dir, toxin_dir |
sp.sense.tomography |
sensor:tomography |
organ tomography |
cavity, strain, support, collapse_proximity |
sp.sense.spectral |
sensor:spectral |
organ spectral |
bands (list of 3) |
sp.sense.seam_coherence |
sensor:seam_coherence |
organ seam_coherence |
readiness, ready |
sp.sense.meta |
sensor:meta |
organ meta |
conflict, ambiguity |
Notes:
nutrient_dir/toxin_dirare relative neighbour-ring indices (0..3) or-1(flat) — never absolute coordinates.attractantis the apparent attractiveness; a mimic inflates it.meta'sconflictis the only signal that exposes the apparent-vs-hidden-danger mismatch — i.e. new senses unlock new information regimes.
Observation feature catalogue (versioned schema)
The 29-feature observation schema is SP.Interface.observation_catalogue/0,
version SP.Interface.catalogue_version/0 ("obs-v1"). Each {source, key} is
mapped to an opaque integer channel by a per-seed permutation; with
scramble: true (default) values also pass through a per-channel invertible
affine. The encoded observation is %{channel_id => float} — nothing else.
Agent / orchestration signals
Agents and spawned probes communicate via signals carried in Emit / Schedule
directives (Jido invariant #6 — no direct shared-state coupling). Recommended
conventions:
| type | source | purpose |
|---|---|---|
sp.probe.report |
worker:<ref> |
an ephemeral probe returns a finding |
sp.agent.intent |
agent:<id> |
inter-agent coordination |
These are application-level conventions for the live runtime; the single-agent
pure core does not require them (it interprets Actuate directives directly).
Validation
- Every emitted signal passes
SP.Core.Signal.valid?/1(tested inSP.Body.SensorTest,SP.InvariantsTest#4). - Payloads pass
SP.Interface.Audit.sensor_payload_ok?/1— no material IDs, no coordinates (Invariant #5).
sha256 b9f2e0b38f3abf60 — of the original file, so what was ingested stays checkable.
Plain — written for this website, not the source document
This is a reference page listing every signal the body can produce, and what each one carries.
All signals share a standard envelope, and one detail matters: the time on a signal is the world's own tick count, never a clock reading.
The table gives one row per sense. Each row says which organ has to exist and be mature before that sense emits anything at all, and which values it carries. Two notes below the table are worth the visit. Directions are given as relative neighbour indices rather than positions. And one sense is the only thing that exposes a mismatch between how attractive something appears and what is actually hidden there. That is how a new sense opens a new kind of information, rather than just more of the same.
The page is explicit that the learner does not see any of this directly. It sees a numbered projection with the meanings stripped out. The semantic view here is for engineers.
Plain · written 2026-08-01 by claude-opus-5 · not yet checked by a person · about the document whose sha256 is b9f2e0b38f3abf60
Clear — written for this website, not the source document
This is a reference catalogue of signals, written for engineers rather than for the learner.
It begins with the envelope. Every signal carries a standard set of attributes, and two of them are constrained. The time field is the logical world tick and never a clock reading. The type must follow a dotted reverse-domain form that is checked by pattern.
A framing paragraph then draws the important boundary. Sensor signals are produced by the body's sensing component and are free of coordinates and material identities by construction. The learner does not see these signals at all; it sees a projection into numbered channels with the meanings removed. The semantic payloads shown on this page are described as the engineering view.
The main table gives one row per sense: the type, its source, the condition under which it is emitted, and the keys it carries. One sense is always available as the starting organ; the rest emit nothing until their organ exists and is mature. The senses cover the body's own internal state, contact chemistry and texture, a sense of the body's own configuration, distal gradients, hidden structure such as cavities and strain, spectral bands, readiness for expansion, and a meta sense.
Two notes follow the table and carry the most meaning. Directional values are relative neighbour indices, or a value meaning flat, and never absolute positions. And one value in the shallow chemical sense is only the apparent attractiveness, which a deceptive organism can inflate; the meta sense is the only place where the mismatch between appearance and hidden danger surfaces. The page draws the general point from that: a new sense unlocks a new information regime rather than simply more readings.
A short section describes the versioned observation schema. Each source and key pair is mapped to an opaque channel by a per-seed permutation, and values may additionally pass through a reversible per-channel transformation. The encoded observation is nothing but channel numbers mapped to values.
A further section covers signals used for coordination between agents and spawned probes, carried in instructions rather than shared state. It is careful to say these are conventions for a live runtime that the single-agent pure core does not require.
The page ends with the validation that every emitted signal must pass, and the audit that keeps material identities and coordinates out of payloads.
Clear · written 2026-08-01 by claude-opus-5 · not yet checked by a person · about the document whose sha256 is b9f2e0b38f3abf60