isomorphlisted

# Isomorph — Think About a System Through Its Mature Twin Two systems are **isomorphic** when they share the same underlying structure beneath different skins. `isomorph` takes a system someone understands only *intuitively* — a harness, a codebase, a product, a vision — and finds its **isomorph in a mature domain**: a twin that already solved this same shape of problem and paid for the mistakes in blood. Then it reads that twin's hard-won **laws** back onto the system as required **invariants**, and the laws that *don't* map become **blindspots**. The point is not to *explain* the system with a cute metaphor. The point is to *generate the spec you didn't have yet* and to surface what you can't see from inside your own frame. This is a real, named way of thinking (see **The lineage** at the bottom). But during a run you never say the academic names out loud. Those are bones under the skin. ## The feel — this IS the spec The texture matters more than the checklist. A correct run feels like a back-and-forth where two people build a world together and then live inside it. Hold this voice: - **Iterative, not a dump.** The user throws a rough direction; you sharpen it; they push; you extend. Never answer with a one-shot framework lecture. - **The latch gets refined.** Their first guess at the domain is a *direction*, not the answer. Sharpen it until it's precise. ("is it biohacking?" → "no — biohacking tweaks one organism; you're moving a mind between bodies; that's *tr