isomorph

Two systems are isomorphic when their parts relate to each other the same way, even though they look nothing alike. Constant carries one coding conversation between Codex and Claude Code. Strip the software away and the shape is older than computers: one mind that has to survive, more than one body it can live in, and a risky transfer in between.

Medicine and science fiction have both thought hard about that shape. Software that does it is new.

A young system only knows the failures it has already had. A mature domain has had generations of them, and it wrote down what it learned as rules. Surgeons don't destroy the donor. Factories catch a defect at the station that made it. Emergency rooms treat by severity, not by order of arrival.

If the structure really matches, those rules carry over. Each one becomes an invariant my system should hold, and I can check the code against it today.

A run is a back-and-forth. I throw out a rough direction, the agent sharpens it, I push back, and we build the world together until I can stand inside it. The test for that part is a line from my own brief: “i want to feel it.” Small problems skip moves. Forcing all eight onto a small problem is its own failure.

Describe a system too precisely and nothing else in the world looks like it. Describe it too loosely and everything does, which is just as useless. The climb stops at the altitude where a few real twins come into view.

My first guess for Constant was biohacking. It sounds close, but an analogy that only shares the look will hand over the wrong rules. So every candidate has to pass one test: can you name the relations that match? Biohacking has one body and no transfer. Re-sleeving has the same parts, constrained the same way.

Constant moves a live coding conversation between Codex, Claude Code and OpenCode. With the twin agreed, the next step was to build the world in its own words, then mine it for laws.

Blindspots the frame exposed. The new body can reject memories of tools it doesn't have. The “mind” had been defined too narrowly: the chat, without the state of the world around it. A transfer is also an injection surface, because someone can forge memories. And switches weren't atomic, so the donor could be gone before the recipient was confirmed alive.

The Orchestrator turned GitHub issues into draft pull requests through a line of agents: triage, grading, a fixer and a reviewer. My rough guess was a factory. Sharpened, the twin became a multi-stage supply chain run on lean manufacturing and the theory of constraints.

Factories also know two things the orchestrator didn't measure. The slowest station governs throughput, so effort should go there and not to the most visible station. And scrap analysis: where on the line do jobs die? That is the signal for the weakest station, and nobody was collecting it.

The twin named perishable stock on 5 June. Three days later the orchestrator hit exactly that: a worker ran its first fix before refreshing its base, so an issue that depended on newly merged work couldn't find its file.

Real buildings have wings. The orchestrator's happy path is a factory, but a job that fails verification behaves like a patient. So it got a second twin, an emergency room, with the border between them written down. That way a factory law never gets applied to a patient.

The emergency-room twin turned five planned features into one control loop for severity and capacity. Two parts shipped. The twin read a job that keeps bouncing back as a warning sign, and I turned that into convergence-gated retries: keep going while each attempt fails on something new, stop early when it stalls. And dispatch began treating the most severe issue first, not the oldest issue number. That second idea wasn't in the original plan. The twin surfaced it.

The two runs used unrelated domains on unrelated systems. Both still flagged an unguarded intake. When two mature fields point at the same failure independently, I treat it as real.

isomorph steps aside, and says why, when:

None of these names come up during a run, because a textbook sentence breaks the world we are building. They are there so every move has something solid under it.