Reschema

Borrow the relational skeleton of a domain you understand and transfer only the structure that survives an explicit mismatch check.

You're three weeks into learning how the immune system works, and the textbook's parade of cell names won't cohere. Then it half-clicks: this resembles a security operation, with patrols, checkpoints, and most-wanted lists. The details are foreign but the relational pattern feels familiar. That resemblance is either a shortcut or a trap, and there's a procedure for telling which.

RESCHEMA means borrowing the relational skeleton of a domain you understand and transferring only the structure that survives an explicit mismatch check. The cue: surface details are novel but the underlying pattern may exist somewhere you know well. Do it in order: first name the target relations you need to grasp (detection, escalation, memory of past threats), then retrieve more than one source domain (security ops, but also spam filtering), align role to role, and, critically, list the mismatches out loud: real security forces don't attack their own headquarters, so autoimmunity has no analog, and there the analogy must be abandoned. Transfer only what survives. It works when the borrowed schema produces a correct novel inference, a prediction about the new domain you then verify. Never transfer surface similarity as if it were mechanism; analogy by vibes is the named failure mode.