Skip to content

Metonymy

Core Idea

Metonymy substitutes a thing for what it is contiguous with — what it is part of, attached to, used by, located in, caused by, or otherwise associated with by adjacency rather than resemblance. The structural move is referencing via attached element: the part, the locale, the instrument, the institution, the address, or the salient adjacent element takes the place of the whole or the related thing, and the receiver recovers the referent through the contiguity. "The Crown" stands for the monarchy; a brand logo for a corporation; a pointer for the data at its address. What makes metonymy a structural pattern rather than a rhetorical flourish is that the same logic — substitute the contiguous-and-cheap for the actual-and-expensive — recurs across substrates that are not human language at all: pointers in code, neural representation by adjacent activation, legal personhood, brand iconography, navigational landmarks, even genetic markers tagging linked traits.

The signature has a few interacting elements. There is a referent costly to invoke directly. There is a contiguous element — part, locale, instrument, institution, mark, address, marker — attached to it. There is a substitution: the contiguous element used in place of the referent. There is a receiver who recovers the referent through the contiguity. And there is a cost: the substitution is correct only while the contiguity holds. From this follows a characteristic failure mode — a dangling reference when the contiguity breaks but the metonym persists — and a corresponding maintenance discipline: preserving, or auditing, the contiguity to keep the metonym valid. Every metonymic reference is therefore implicitly a bet that the contiguity remains operative, and breaking that contiguity invalidates the reference even though the metonym still names something.

How would you explain it like I'm…

Name By What's Stuck To It

Sometimes we name a thing by pointing at something stuck to it instead. If I say "the kettle is boiling," the kettle isn't boiling — the water inside is, but the kettle is right there holding it, so I just say kettle. You knew what I meant because the two things go together.

Name By What's Attached

Metonymy is when you call something by the name of a thing that's close to it or part of it, instead of using its real name. "The Crown" means the king or queen, because the crown sits on their head. A team's logo can stand for the whole company. This works because the two things are attached or go together, so when you hear one, your brain jumps to the other. It only works as long as they really do stay connected.

Naming by Adjacency

Metonymy swaps in something next to or part of a thing to stand for the thing itself — by adjacency, not by likeness. "The Crown" means the monarchy because a crown belongs to a monarch; "give me a hand" means help because hands do the helping. This is different from metaphor, which works by resemblance ("he's a lion"); metonymy works by connection — part, place, tool, owner, or label standing in for the whole. The cheap, nearby thing substitutes for the costly, real thing, and you recover the real meaning through the link. But the substitution is only correct while that link holds: break the connection and the name points at nothing, even though you can still say it.

 

Metonymy is reference by contiguity: a thing is named through something it is part of, attached to, used by, located in, or otherwise associated with by adjacency rather than resemblance. The structural move is referencing-via-attached-element — a part, a locale, an instrument, an institution, an address, or a salient neighbor takes the place of the whole, and the receiver recovers the intended referent through the contiguity. What makes this a structural pattern and not just a figure of speech is that the same logic — substitute the contiguous-and-cheap for the actual-and-expensive — recurs far outside language: a pointer stands for the data at its memory address, a brand logo for a corporation, a landmark for a location, a genetic marker for a linked trait. Five elements interact: a referent costly to invoke directly, a contiguous element attached to it, a substitution of the one for the other, a receiver who recovers the referent, and a cost — the substitution is valid only while the contiguity holds. From this follows a characteristic failure mode, the dangling reference, where the contiguity breaks but the metonym persists and now names nothing. And it implies a maintenance discipline: preserve or audit the contiguity to keep the reference valid. Every metonym is thus an implicit bet that its link to the referent is still operative.

Structural Signature

a costly-to-invoke referenta contiguous element attached to ita substitution of element for referenta receiver who recovers the referent through the contiguitya validity-condition that the contiguity still holdsa failure mode when the attachment breaks but the proxy persists

The pattern is present when each of the following holds:

  • A referent. Some target entity that is expensive, unwieldy, or distributed to invoke directly — the whole, the institution, the underlying datum.
  • A contiguous element. A second entity bound to the referent by adjacency rather than resemblance: part, locale, instrument, container, mark, address, marker. The binding is a relation of attachment, not of similarity.
  • A substitution. The contiguous element is used in the referent's place — named, manipulated, or transmitted as if it were the referent.
  • A recovering receiver. An interpreter who restores the referent from the proxy by traversing the contiguity. Without a receiver who can make the traversal, the substitution carries no reference.
  • A validity invariant. The substitution is correct only while the attachment holds. This is the load-bearing condition that separates metonymy from arbitrary naming.
  • A contiguity-failure mode. When the attachment breaks but the proxy is still in use, the reference dangles — it still names, but no longer reaches its referent.

These compose into a single move: reference is offloaded onto a cheap attached handle, and the whole arrangement is a standing bet that the attachment remains operative.

What It Is Not

  • Not metaphor. See metaphor. Metaphor substitutes by resemblance across distinct domains ("time is money"); metonymy substitutes by adjacency within a domain ("the Crown" for the monarchy). The diagnostic differs: metaphor asks "in what way is A like B?", metonymy asks "what is A attached to, and does the attachment still hold?"
  • Not the general fact of standing-for. See symbolic_representation. Symbolic representation is the broad relation of one thing conventionally denoting another; metonymy is the specific subtype in which the denoting handle is licensed by attachment rather than by arbitrary convention or by resemblance.
  • Not a causal trace. See indexicality. An index points because the referent caused it — smoke for fire, a footprint for a foot. Metonymy substitutes a salient attached element in deliberate communication; the contiguity need not be causal, and the substitution is chosen, not left behind.
  • Not the sign-pairing itself. See signifier_signified_duality. That prime names the bare fact that every sign couples a signifier to a signified; metonymy specifies how a particular pairing was forged — by adjacency — in a wide class of cases.
  • Not the selection-versus-combination axis. See paradigmatic_vs_syntagmatic_relations. That prime classifies relations as choices-among-alternatives versus chains-of-co-occurrence; metonymy is a referential move, not an axis of relation, even though it exploits syntagmatic (contiguity) structure.
  • Common misclassification. Calling any substitution-by-shorthand "metonymy" when the link is similarity, not attachment. The catch: try relocating the referent. If moving the institution breaks "the Crown," the relation is contiguity (metonymy); if the substitution survives relocation because it rests on a shared quality, it is metaphor.

Broad Use

  • Rhetoric and literature. "Lend me your ears" (ears for attention); journalistic conventions in which a building or capital stands for an institution or government.
  • Branding and semiotics. A logo is the company; the mark stands in by adjacency — it has been on every product — and over time the substitution operates frictionlessly.
  • Programming and computer science. A pointer is referenced through its address: the address (contiguous container) stands for the data (referent). URLs, handles, foreign keys, and symbolic links all instantiate the same move — refer to the data through an attached locator rather than carrying the data itself.
  • Neuroscience. Neural population coding by adjacent activation: a feature is represented by the neurons that fire near it in a topographic map, with neighbors carrying related referents.
  • Law. Institutional substitution and legal personhood: an office or sovereign stands for whoever occupies it; corporations act as legal persons; immunity attaches to office, not occupant.
  • Cartography and genetics. A flagged landmark stands for the surrounding area; a postal code for a neighborhood; a genetic marker contiguous on the chromosome stands in for the linked gene in association studies — linkage is metonymy applied to inheritance.
  • Interface design. A floppy-disk icon means save, a printer icon means print — the instrument-icon-for-operation recognizable because the contiguity has been established.

Clarity

Naming metonymy lets a reader separate it from metaphor — which works by similarity across distinct domains — and recognize when a substitution operates by adjacency instead. This matters because the diagnostic moves differ: metaphors invite "in what way is A like B?"; metonymies invite "what is A attached to, and is that attachment still operative?" When a spokesperson's building stands for an institution's policy, the metonymy rests on a chain of contiguities (spokesperson → building → institution → policy), and the relevant question becomes whether that contiguity still binds the way the substitution presumes. The clarity gain is in surfacing the contiguity as the load-bearing relation, so it can be questioned rather than assumed.

The frame also clarifies a recurrent failure by giving it a single name across substrates: the broken metonymy. A pointer dangles when the data is freed; a brand goes generic when its contiguity to the company dilutes; a genetic marker stops tagging a trait when recombination breaks the linkage; an institutional name no longer signals intent when the parts diverge. Each is the same event — the metonym still refers, but to nothing useful — and naming metonymy makes that common structure visible where domain vocabulary would hide it as four unrelated bugs.

Manages Complexity

Metonymy is compression by referencing via cheap proxies. Carrying the full referent every time would be expensive — the entire institution, the full data structure, the whole neighborhood — while referring through the contiguous handle (the office, the pointer, the landmark) is cheap, durable, and locally available. The complexity of invoking a large or distributed referent is reduced to the complexity of invoking a small attached element that stands in for it. This is why the move recurs wherever direct reference is costly: it lets a system manipulate a compact handle in place of an unwieldy referent.

The compression carries a precise cost the frame keeps in view: the substitution is correct only as long as the contiguity holds. Managing complexity through metonymy therefore means managing the contiguity — keeping the handle bound to its referent, or auditing whether the binding still holds. The benefit (cheap, local reference) and the liability (silent invalidation when the contiguity breaks) are two sides of one structural fact, and a system that exploits the first without disciplining the second accumulates dangling references.

Abstract Reasoning

The pattern supports reasoning about when substitution is safe and when it breaks. A pointer dangles if its data is freed; a brand becomes generic when its contiguity to the company dilutes; a genetic marker stops tagging a trait when recombination breaks the linkage; an institutional name no longer reliably signals intent if its parts diverge. Each is a contiguity failure — the metonym still refers, but to nothing useful — and recognizing the shared structure gives metonymy diagnostic force: every metonymic reference is implicitly a bet that the contiguity remains operative, and naming the bet reveals when it is about to be called.

Reasoning at this level asks, of any reference-by-proxy: what is the referent, what contiguous element stands in for it, does the receiver recover the referent through that contiguity, and what would break the contiguity while leaving the handle in place? These questions distinguish metonymy from metaphor (substitution by resemblance across distinct domains, versus contiguity within a domain), from symbolic representation generally (the broad fact of standing-for by convention, of which metonymy is the specific subtype licensed by attachment), from indexicality (which emphasizes traces of causation — smoke for fire — where metonymy emphasizes substitution via a salient attached element in deliberate communication), from synecdoche (strictly part-for-whole, a sub-case of metonymy in most classifications), and from the signifier-signified pairing in any sign (where metonymy specifies how the pairing was forged in a wide class of cases).

Knowledge Transfer

The pattern transfers as a contiguity-auditing discipline, carried by stable role mappings: the referent maps to the institution, the data structure, the neighborhood, the linked gene, the company; the contiguous element maps to the office, the pointer, the landmark, the marker, the logo; the substitution maps to the reference-by-handle in each substrate; and the failure mode maps to the dangling reference, the generic trademark, the broken linkage, the diverged institution. With these fixed, a systems programmer reasoning about pointer lifetimes and a brand strategist reasoning about trademark dilution recognize the same problem.

The single transferable intervention is to make the contiguity explicit and audit whether it still holds. In software this maps to pointer-safety reasoning — lifetimes, ownership, reference counting are all disciplines for preserving the contiguity between handle and referent. In brand strategy it maps to contiguity maintenance — continuing to deliver on the association the mark trades on. In legal practice it maps to the doctrine of looking past the institutional handle when the contiguity between officer and corporation no longer protects the substitution. In neuroscience it maps to receptive-field plasticity, where the adjacency that licensed a population code shifts. A use-after-free bug — a pointer that survives the freeing of the struct it named, now reading garbage — is the cleanest non-linguistic instance: the metonym (the pointer) persists after the contiguity (address → struct) is broken, exactly the structure of a press release attributed to an institution whose parts have diverged or a logo on a counterfeit product whose contiguity to the manufacturer has been forged. The transfer is robust because the strip-the-jargon residue — substitution-via-attached-handle, valid only while the attachment holds — survives into rhetoric, code, neural coding, law, cartography, and genetics alike, several of them non-human substrates where the structural move appears without translation. The pointer-safety case deserves prominence precisely because programmers reason explicitly about lifetimes and ownership, having learned the cost of broken contiguities that other domains reason about only implicitly; promoting the pattern makes that discipline transferable.

Examples

Formal/abstract

Consider a pointer in a manually-managed memory model — a C program holding struct Account *p. The referent is the account record: a sixteen-byte structure living at some heap address, costly to copy and carry by value. The contiguous element is the address itself, an eight-byte integer bound to the record purely by location, not by any resemblance to its contents. The substitution is the program's pervasive use of p in place of the record: it passes p to functions, stores p in lists, compares p to other pointers — manipulating the cheap attached handle as if it were the unwieldy referent. The receiver that recovers the referent is the dereference operation *p, which traverses the contiguity (address → bytes) to reach the account. The validity invariant is exact: the substitution is correct only while the address still maps to the live record. The instant free(p) runs, the contiguity breaks — the address is recycled — yet p still holds the same integer. A subsequent *p is a use-after-free: the metonym persists, names a location, but no longer reaches its referent. The diagnosis the frame yields is the discipline that prevents this: ownership and lifetime reasoning are nothing more than auditing whether the address-to-record contiguity still holds at every dereference. Reference counting, borrow checking, and RAII are three engineering mechanisms for keeping the metonym valid — each one a formal contiguity-maintenance protocol.

Mapped back: The pointer is the contiguous element, the record the referent, dereference the recovering receiver, and the use-after-free the contiguity-failure mode — metonymy with the linguistic vocabulary stripped away entirely.

Applied/industry

In trademark law and brand strategy, "the Swoosh" stands for an entire athletic-apparel corporation. The referent is the company — its quality, its supply chain, its reputation — distributed and impossible to invoke directly on a shoe. The contiguous element is the mark, bound to the company only by a history of appearing on its products, not by any visual resemblance to athletics. The substitution is the consumer's and the market's treatment of the logo as a sufficient stand-in: the mark on a box licenses a purchase decision, a price premium, a trust judgment. The receiver is the consumer who recovers "this is genuinely that company's product, with its quality guarantees" by traversing the established contiguity. The validity invariant is that the substitution holds only while the attachment between mark and company is real and exclusive. Two characteristic failures map onto the frame's contiguity-failure mode. A counterfeit forges the contiguity: the mark appears, but the attachment to the manufacturer is fake, so the metonym names the company while reaching a counterfeiter's factory — exactly a dangling reference deliberately planted. Genericide dilutes it: when "escalator" or "aspirin" detaches from its originating firm and comes to name a whole product class, the metonym still refers but no longer reaches the specific company. The interventions the frame prescribes are precisely what trademark practice does: enforcement actions (suing counterfeiters) repair forged contiguities, and active policing of generic usage (Xerox's "don't say xerox, say photocopy" campaigns) preserves the attachment before it dilutes. The same move appears in cartography and epidemiology: a postal code stands for a neighborhood, and contact-tracers use a flagged location as a metonym for everyone contiguous to it — valid only while the population-to-place attachment holds.

Mapped back: The logo is the contiguous element, the corporation the referent, the consumer the recovering receiver, and counterfeiting and genericide the two ways the attachment breaks while the proxy persists — the identical structure to a dangling pointer, operating in commerce rather than memory.

Structural Tensions

T1 — Contiguity versus Resemblance (Boundary with Metaphor). Metonymy substitutes by adjacency; metaphor substitutes by similarity across distinct domains. The two are not always cleanly separable — "the White House" trades on both location and an aura of institutional gravity — and the same expression can shade from one to the other as the literal contiguity fades. The failure mode is misdiagnosis: treating a metonym as a metaphor invites "in what way is A like B?" when the live question is "what is A attached to, and does the attachment still hold?" The diagnostic is to ask whether the substitution would survive moving the referent: if relocating the institution breaks "the Crown," the relation is contiguity, not resemblance.

T2 — Validity Now versus Validity Later (Temporal Drift). A metonym is correct only while its contiguity holds, but contiguities decay on their own timescale — pointers outlive their allocations, trademarks dilute, institutional names diverge from the parts that once justified them. The substitution carries no internal clock signaling when its warrant has lapsed. The failure mode is the silent dangling reference: the metonym keeps naming, fluently and confidently, after it has stopped reaching anything useful. The diagnostic is to date the contiguity, not the metonym — ask when the attachment was last verified, since the proxy's continued availability says nothing about whether the binding behind it survives.

T3 — Compression Gain versus Audit Cost (the Maintenance Trade). Metonymy's value is that the cheap handle is locally available while the referent is expensive or distributed; its liability is that keeping the handle bound requires ongoing contiguity maintenance the substitution itself hides. A system can bank the compression gain immediately but defers the audit cost indefinitely, which is why dangling references accumulate. The failure mode is exploiting the cheap reference while neglecting the discipline that keeps it valid — using pointers without lifetime reasoning, trademarks without policing. The diagnostic: for every metonym in heavy use, name who is responsible for maintaining its contiguity, and treat an unowned binding as already suspect.

T4 — Sender's Contiguity versus Receiver's Traversal (Shared-Ground Scope). The substitution carries reference only if a receiver can traverse the same contiguity the sender assumed; reference is not in the handle but in the shared path from handle to referent. When sender and receiver inhabit different contexts, the traversal fails even though the contiguity objectively holds — an insider's institutional shorthand reaches nothing for an outsider. The failure mode is presuming a private contiguity is common ground, producing references that dangle for the audience while seeming solid to the author. The diagnostic is to ask whether the receiver shares the path, not merely whether the attachment exists: a valid contiguity no one else can traverse still fails as reference.

T5 — Forged Contiguity versus Genuine Attachment (Adversarial Direction). Most metonymy analysis assumes contiguities break by decay; but a contiguity can also be deliberately fabricated, so the metonym reaches a referent the receiver did not intend. A counterfeit Swoosh, a spoofed sender address, a phishing domain contiguous-by-design to a trusted brand — each plants a dangling reference on purpose, exploiting the receiver's habit of trusting the handle. The failure mode is treating the proxy as self-authenticating: the mark's mere presence is taken as proof of the attachment it claims. The diagnostic is to verify the contiguity against an independent channel rather than reading it off the handle, since the handle is exactly what an adversary controls.

T6 — Part-for-Whole Selection versus Distortion (Which Handle Bias). A referent has many contiguous elements, and choosing one to stand for the whole is never neutral — the salient part foregrounds some aspects and suppresses others ("boots on the ground" makes a war about infantry, not policy). Metonymy treats the substitution as a transparent convenience, but the selection of handle silently editorializes. The failure mode is mistaking the chosen proxy for an unbiased pointer to the referent, importing the framing baked into which part was elevated. The diagnostic is to enumerate the alternative contiguous handles that were available and ask what each would have foregrounded; a metonym with no live alternatives is doing more rhetorical work than it admits.

Structural–Framed Character

Metonymy sits just on the structural side of the middle of the structural–framed spectrum — a mixed-structural prime. Its core move (refer to a referent through a contiguous element attached to it, valid only while the attachment holds) is a bare relational pattern, but the prime carries a faint residue of its rhetorical home, which is what keeps it from reading as cleanly structural as feedback or minimal pairs.

The diagnostics that pull it toward structural dominate. On human-practice-bound, the move plainly runs in non-human substrates indifferent to any speaker: a C pointer reaching its struct through an address, a topographic neural map representing a feature by adjacent activation, a genetic marker tagging a linked trait by physical contiguity on the chromosome — each is metonymy with no human interpreter in the loop, the substitution licensed by attachment rather than by anyone's intention. On evaluative_weight it is flatly neutral: a metonym is neither apt nor faulty until you specify what it does, and a dangling pointer is a bug only relative to a goal, not inherently. On import_vs_recognize, invoking the prime mostly recognizes a contiguity already wired into the system — the address-to-bytes mapping, the marker-to-gene linkage exist whether or not anyone names them "metonymy."

What keeps it from a pure-structural zero is the home vocabulary and origin. The diagnostic that splits is vocab_travels: the residue of rhetoric — "referent," "substitution," "stands for" — lingers, and a domain can usually re-tell the pattern in its own words (lifetimes, linkage, population coding) only after the structural skeleton is extracted, so the home lexicon travels half-attached rather than dropping away entirely. Institutional_origin reads as partial for the same reason: the prime was born in literary-rhetorical theory, and that ancestry tints it even though the move itself is substrate-agnostic. This split — non-human substrates and value-neutrality pulling structural, a rhetorical lexicon and origin pulling framed — is exactly what the mixed-structural label with its 0.4 aggregate records: predominantly structural, with a thin inherited frame that never fully detaches.

Substrate Independence

Metonymy is a strongly substrate-independent prime — composite 4 / 5 on the substrate-independence scale. Its domain breadth is maximal: the substitute-the-contiguous-handle-for-the-costly-referent move recurs in rhetoric and branding, in pointers and foreign keys in code, in topographic neural population coding, in legal personhood, in cartographic landmarks and postal codes, and in genetic linkage markers — several of these non-human substrates where no speaker is in the loop, so the pattern is recognized rather than translated when it surfaces. The signature is highly relational — referent, contiguous element, substitution, recovering receiver, validity-while-attached, dangling-failure — stated in pure attachment terms with no commitment to language, which is why a use-after-free pointer and a counterfeit trademark and a recombination-broken marker read as one structure. Transfer is concrete and well documented: ownership-and-lifetime reasoning in software, trademark policing in commerce, and linkage analysis in genetics are the same contiguity-auditing discipline under different names. What holds it a notch below 5 is the residue of its rhetorical origin — the home lexicon ("referent," "stands for") travels half-attached and must be stripped before each domain re-tells the move in its own words — but the structural skeleton itself reaches into physical and biological substrates without translation.

  • Composite substrate independence — 4 / 5
  • Domain breadth — 5 / 5
  • Structural abstraction — 4 / 5
  • Transfer evidence — 4 / 5

Relationships to Other Primes

One-hop neighborhood: parents above, mutual partners to the right, children below.Metonymysubsumption: Symbolic RepresentationSymbolicRepresentation

Parents (1) — more general patterns this builds on

  • Metonymy is a kind of Symbolic Representation

    The file: metonymy is 'the specific sub-mechanism' of standing-for licensed by ATTACHMENT/contiguity rather than resemblance or arbitrary convention — a species of symbolic_representation (the genus). Add symbolic_representation as parent.

Path to root: MetonymySymbolic RepresentationRepresentationAbstraction

Neighborhood in Abstraction Space

Metonymy sits in a sparse region of abstraction space (74th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely rather than landing on a neighbor.

Family — Identity Matching & Lookup (10 primes)

Nearest neighbors

Computed from structural-signature embeddings · 2026-06-14

Not to Be Confused With

The deepest confusion is with metaphor, the other great figure of substitution. Both replace a referent with something else, and a thoughtful reader can lose the seam because some expressions ride both at once ("the White House said" leans on location, but "the White House" also carries an aura of executive gravity). The structural invariant that separates them is the kind of relation licensing the swap. Metaphor's relation is resemblance across a domain boundary: it maps structure from a source ("a sea of troubles") onto a target that is genuinely unlike it, and the transfer survives moving either term because it rests on shared abstract shape, not physical adjacency. Metonymy's relation is attachment within a domain: the proxy reaches the referent only by a concrete contiguity — part, locale, instrument, institution — and the substitution dies the instant that adjacency is severed. What metaphor captures that metonymy cannot is cross-domain insight: it manufactures a new likeness, teaching you to see one thing as another. What metonymy captures that metaphor cannot is reference economy under a maintained binding: it cheaply names something via a handle that must be kept attached. Treat the relabeling test as load-bearing — a metaphor's force is undamaged by relocating the referent; a metonym's collapses.

A subtler confusion is with indexicality. Both connect a sign to its referent by a real-world, non-arbitrary link rather than by convention, and both fail when that link is broken. But indexicality's defining relation is causal trace: the index exists because the referent produced it — smoke caused by fire, a footprint pressed by a foot, a fever symptomatic of infection — and reading the index is inference backward along a causal chain. Metonymy's relation is deliberate substitution via a salient attached element, and the attachment need not be causal at all (a logo is contiguous to a company by history, not causation; an office is contiguous to its occupant by institutional definition). The roles differ accordingly: an index is evidence left behind and read by a detective; a metonym is a handle chosen and transmitted by a sender who intends the receiver to traverse the contiguity. Indexicality is about what a sign betrays about its cause; metonymy is about what a communicator economizes by naming through an attachment. The two overlap where a causal trace is also pressed into communicative service, but the analytic question diverges: for an index ask "what caused this?", for a metonym ask "what is this attached to, and was the attachment chosen to stand in?"

Finally, metonymy is distinct from symbolic_representation as a species is from its genus. Symbolic representation names the broad capacity for one thing to stand for another by convention — the bare standing-for relation that subsumes icons, indices, arbitrary signs, and metonyms alike. Metonymy is the specific sub-mechanism in which the standing-for is licensed neither by resemblance (icon) nor by sheer arbitrary convention (the word "dog") but by attachment. Collapsing metonymy into symbolic representation loses exactly the diagnostic payload — the validity-while-attached invariant and its dangling-reference failure mode — that makes the prime useful; conversely, treating every symbol as a metonym wrongly imports a contiguity audit where the binding is merely conventional and has no attachment to decay.

These distinctions matter because the maintenance discipline each implies is different. A metaphor needs no contiguity audit — there is no attachment to break, only an interpretive likeness to keep apt. An index needs no maintenance at all — it is read forensically, not maintained. Only a metonym carries the standing liability the prime foregrounds: a handle that must be kept bound to its referent on pain of silent, fluent, dangling reference. Sorting a substitution into the right bin tells a practitioner whether to audit an attachment (metonymy), reinterpret a likeness (metaphor), or trace a cause (indexicality).

Solution Archetypes

No catalogued solution archetypes reference this prime yet.