← All work

Phenotype

Expressing the genome substrate into a running agent

Last devlog: June 21, 2026

THE EXPRESSION LAYER — GENOME SUBSTRATE INTO RUNNING AGENT ← EXECUTE SIDE · CANNOT RESOLVE INTENT → CONTINUOUS PATH — STRUCTURALLY ENFORCED, RUNS UNATTENDED Gene LibraryValidated · pinned versionconsumed from genome · never modifiedContract GateFour-check compositestatic analysis · runs offlineComposition→ Running Agentdeterministic · the hot pathAgentruns in gapsunattendedBoundary Enforcementclosed-sum types · AST scans · signature introspectionevery declared-input construction scanned — query-derivation fails the buildDECLARED-INPUT SURFACE — INTENT ENTERS FROM OUTSIDE, AS HUMAN ACT Declared-Input SurfaceThe one place intent-resolution entersroles · scopes · grants · elevation — from outside, declared, never derivedHumandeclares acts · blocks episodic pathcandidate geneadmitted onlydeclared actsdeclares

Key boundary: The execute side (genes composing, the agent running) can detect conflict and execute a declared resolution, but it can never resolve intent. Intent-resolution enters only through the declared-input surface, as a human's declared act. The line between "execute a declared resolution" and "resolve intent" is the whole architecture.

Why it matters: If the execute side could derive a declared input from the query, the system would be quietly resolving intent while appearing not to — the boundary eroding while looking intact. The structural checks make that failure fail the build instead of passing silently.

Notable decision: The continuous path is enforced entirely by construction, so the boundary holds in the cold gaps when the operator is away and cannot defend it. Human judgment enters only on the episodic path — a new gene, a new declared-input class — and that path blocks for the operator rather than proceeding without them. The boundary that can't be made structural is named and watched, never hidden.

Phenotype is the expression layer for the Digital Genome — the runtime that takes a proven substrate (agent behavior composed from discrete, inspectable genes) and makes it into a working agent. The genome is the genotype; Phenotype is the genotype expressed in an environment. The name carries the boundary finding: the expression depends on something outside the substrate, which is where the human's declared act enters.

The architecture has two sides separated by a structural boundary. The execute side (genes composing, the agent running) can detect conflict and execute a declared resolution, but it can never resolve intent — intent enters only through the declared-input surface, as a human's declared act. The boundary is enforced by construction: closed-sum types, AST scans, signature introspection. Every declared-input construction is scanned; a query-derivation fails the build.

The continuous path runs unattended — structurally enforced, no judgment calls required. The episodic path (a new gene, a new declared-input class) blocks for the operator. The boundary that can't be made structural is named and watched, never hidden. This is the genome boundary finding applied to the operator's own cadence: structural enforcement runs in the gaps; human judgment enters only where it must, and blocks rather than proceeding without it.

Devlog posts about Phenotype

The first off-shape gene

We built a gate to decide what counts as a gene, then built the first thing it wasn't shaped for and ran it through — hoping it would break. It did, and the break told us what the gate had been quietly assuming all along.