Remapping¶
Core Idea¶
Remapping is the pattern in which a single substrate — the same physical or logical units — holds multiple, context-keyed, disjoint representations and switches between them discretely on a context cue. The inactive maps are preserved for recovery, so the system gains multi-environment flexibility without paying for multiple parallel substrates.
How would you explain it like I'm…
Two Toy Boxes
Map-Swapping Brain
Context-Keyed Map Switching
Broad Use¶
- Neuroscience: hippocampal place cells fire at uncorrelated locations across environments, the same neuron participating in many maps.
- Object-oriented programming: one method name resolves to different implementations by dispatch context.
- Multi-tenant software: shared infrastructure presents each tenant a tenant-keyed view of the same physical records.
- Social systems: a person reorganizes their behavioural repertoire on entering a role (judge, parent, teacher).
- Bilingual cognition: the same content reorganizes lexically and grammatically on a language-context switch.
- Configuration-driven software: one binary reorganizes its behaviour on reading different config files.
Clarity¶
Resolves "the system behaves differently in different contexts" into multiple simple representations plus a context-recognition gate, rather than one complicated representation — easier to reason about and to debug.
Manages Complexity¶
One substrate hosting N disjoint maps is far simpler to maintain than N parallel substrates kept mutually consistent, and faults sort cleanly into wrong-map (gate) errors versus within-map errors.
Abstract Reasoning¶
The formal shape is a function from substrate-state and context to an effective representation, where the context argument carries all the load separate substrates would otherwise bear — licensing "build context recognition over a shared substrate, not parallel substrates."
Knowledge Transfer¶
- Neuroscience → engineering: "audit the context-recognition gate first" maps place-cell cue-dropout onto the multi-tenant bug of a lost tenant ID serving one customer's data to another.
- Hippocampus → ops: "preserve inactive maps" maps environment-A retention onto not deleting one tenant's view when another deploys.
- Spatial cognition → distributed systems: "log the context cue with every action" maps environment-recognition onto propagating context across async boundaries.
Example¶
A multi-tenant platform leaks one customer's data to another because the tenant-ID cue is lost in an async callback, so the shared query layer falls back to a default scope — structurally the same as a rat losing its environment cues and activating the wrong spatial map.
Relationships to Other Primes¶
Foundational — no parent edges in the catalog.
Children (1) — more specific cases that build on this
- Code-Switching is a kind of, typical Remapping — The file: 'code_switching is the HUMAN PRACTICE... remapping is the substrate-neutral architecture (one substrate, context-keyed maps) of which code-switching is one instance.' Admit remapping as the more-general parent; add it as an additional parent of code_switching (which keeps its contextual_mode_switching lineage).
Not to Be Confused With¶
- Remapping is not Transfer of Learning because remapping holds the substrate fixed and switches the representation, whereas transfer holds the representation fixed and ports it across contexts.
- Remapping is not Cognitive Reframing because remapping selects a different stored map and leaves the others intact, whereas reframing edits the single representation in play.
- Remapping is not Transformation because remapping switches between statistically independent maps with no rule relating them, whereas transformation is a rule-governed continuous mapping from one representation to another.