Skip to content

Alias-to-Authority Mapping

Prime #
1265
Origin domain
Linguistics & Semiotics
Subdomain
identity management → Linguistics & Semiotics

Core Idea

Alias-to-authority mapping is the commitment to keep one canonical form for a referent — its authority record — while maintaining a many-to-one routing layer from every variant label that users actually type, search for, cite, or import. The variant labels are first-class: recorded, searchable, redirectable. But they are not identities of their own; they all resolve to the same authority form. The result is that the referent has one identity for the purposes of counting, deduplication, linking, and ownership, while remaining reachable through every name by which any user has ever encountered it. The pattern commits four roles to travel together: an authority form (the chosen canonical label, often arbitrary among the variants but deliberately fixed); a variant set (every alternative label known to map here — spellings, translations, abbreviations, former names, even misspellings); a resolution function that routes any variant query to the authority form; and a stability contract that the authority form will outlive the variants and that newly discovered variants will be added to the mapping rather than promoted to new authorities.

The load-bearing feature is asymmetry. This is not a flat synonym list, which treats labels as peers; one form is privileged, the others route to it, and the direction of routing carries operational consequences — which name appears in counts, which gets cited, which the system commits to maintaining. A synonym set lets any member stand for the group; an alias-to-authority mapping insists that exactly one member is the identity and the rest are reachable surfaces. That asymmetry is what lets identity aggregate correctly even as the surface labels proliferate without bound.

How would you explain it like I'm…

All Your Names, One You

Imagine a kid named Robert who's also called Bob, Bobby, and Rob. The teacher picks one real name for the roll call, but knows all the nicknames point to the same kid. So no matter which nickname you say, she finds the one Robert. He's counted once, but you can reach him by any name.

Many Names, One Record

Alias-to-Authority Mapping is when you pick ONE official name for something (call it the authority record) and then keep a list of every other name people actually type, search, or cite, all pointing to that one official name. The other names are real and useful, you can search them and they redirect you, but they aren't separate identities; they all resolve to the same authority form. That way, when you count things or check for duplicates or link to it, there's exactly one identity, even though people can reach it by any nickname, spelling, or old name they remember. The key is that it's lopsided on purpose: one name is the real identity, and all the rest just route to it.

Aliases Route to the Authority

Alias-to-Authority Mapping is the commitment to keep *one* canonical form for a referent — its authority record — while maintaining a many-to-one routing layer from every variant label users actually type, search for, cite, or import. Variant labels are first-class: recorded, searchable, redirectable — but they are *not* identities of their own; they all resolve to the authority form. So the referent has a single identity for counting, deduplication, linking, and ownership, while staying reachable through every name anyone has used. Four roles travel together: an *authority form* (the chosen canonical label), a *variant set* (every alternative — spellings, translations, abbreviations, former names, even misspellings), a *resolution function* routing any variant to the authority form, and a *stability contract* that the authority form outlives the variants and new variants get added rather than promoted. The key feature is *asymmetry*: unlike a flat synonym list where labels are peers, here exactly one form is the identity and the rest are reachable surfaces — and the routing direction decides which name appears in counts, gets cited, and is maintained.

 

Alias-to-Authority Mapping is the commitment to keep *one* canonical form for a referent — its authority record — while maintaining a many-to-one routing layer from every variant label that users actually type, search for, cite, or import. The variant labels are first-class: recorded, searchable, redirectable. But they are *not* identities of their own; they all resolve to the same authority form. The result is that the referent has one identity for the purposes of counting, deduplication, linking, and ownership, while remaining reachable through every name by which any user has ever encountered it. The pattern commits four roles to travel together: an *authority form* (the chosen canonical label, often arbitrary among the variants but deliberately fixed); a *variant set* (every alternative label known to map here — spellings, translations, abbreviations, former names, even misspellings); a *resolution function* that routes any variant query to the authority form; and a *stability contract* that the authority form will outlive the variants and that newly discovered variants will be added to the mapping rather than promoted to new authorities. The load-bearing feature is *asymmetry*. This is not a flat synonym list, which treats labels as peers; one form is privileged, the others route to it, and the direction of routing carries operational consequences — which name appears in counts, which gets cited, which the system commits to maintaining. A synonym set lets any member stand for the group; an alias-to-authority mapping insists that exactly one member is the identity and the rest are reachable surfaces. That asymmetry is what lets identity aggregate correctly even as the surface labels proliferate without bound.

Structural Signature

the single authority form (canonical label) — the variant set (every alternative label) — the resolution function routing variant to authority — the stability contract — the many-to-one asymmetry — the aggregation property on which downstream counting depends

The pattern is present when each of the following holds:

  • An authority form. One canonical label is deliberately fixed as the referent's identity for counting, deduplication, linking, and ownership — often arbitrary among the variants, but privileged.
  • A variant set. Every alternative label known to map here — spellings, translations, abbreviations, former names, even misspellings — is recorded, searchable, and redirectable, but is not an identity of its own.
  • A resolution function. A defined operation routes any variant query to the authority form, so the referent is reachable by any name.
  • A stability contract. The authority form is committed to outlive the variants, and newly discovered variants are added to the mapping rather than promoted to new authorities.
  • The many-to-one asymmetry. Exactly one form is the identity; the rest are reachable surfaces that route to it. This is the load-bearing feature: it distinguishes the pattern from a flat synonym list, where labels are peers and any member can stand for the group, and the direction of routing carries operational consequences — which name appears in counts, which gets cited, which the system maintains.
  • The aggregation property. Interactions reaching the referent through any label accrue to the same identity, so identity aggregates correctly even as surface labels proliferate without bound.

Two tests confirm the pattern operatively: the aggregation test (do interactions via different labels accrue to one identity?) and the maintenance test (is there a defined operation that updates the authority while leaving variant routing intact?). A relabeling is a controlled promotion of a variant to authority and demotion of the prior authority to alias, performed without breaking routing. Lose the asymmetry and the mapping collapses into a synonym list with no identity to aggregate to.

What It Is Not

  • Not access_control. Access control governs who may reach or operate on a resource; alias-to-authority mapping governs by which names a resource is reachable and which name is its identity. The embedding proximity comes from "access point" wording, but one is about permission, the other about routing labels to a canonical referent.
  • Not versioning. Versioning orders successive states of one evolving thing; alias-to-authority routes many coexisting labels to one current authority form. A version chain is temporal succession; the alias mapping is many-to-one naming at a point in time.
  • Not indirection. Indirection inserts a resolvable level between reference and target generically; alias-to-authority is the specific asymmetric many-to-one routing that makes identity aggregate. Indirection is the mechanism; the aggregation-bearing asymmetry is what distinguishes this prime.
  • Not provenance. Provenance records where a record came from; alias-to-authority records which surface labels denote one canonical identity. One is origin-history; the other is name-to-identity routing.
  • Not traceability. Traceability links artifacts across a chain so origins can be followed; alias-to-authority collapses many names onto one identity so interactions aggregate. Tracing follows a thread of distinct things; aliasing unifies many labels into one referent.
  • Not a flat synonym set. A synonym set treats labels as peers, any of which can stand for the group; alias-to-authority privileges exactly one form as the identity and routes the rest to it. Losing that asymmetry collapses the pattern into mere synonymy with no identity to aggregate to.
  • Common misclassification. Calling a "preferred name" field alias-to-authority. The catch is the aggregation and maintenance tests: if interactions via different labels do not accrue to one identity, or there is no operation that updates the authority while preserving variant routing, this is a label preference on a fragmented identity, not a true authority mapping.

Broad Use

The same wiring — many surface labels, one authoritative referent, an explicit routing layer, and a contract about which side bears responsibility for the maintained identity — appears across substrates. In library and archival authority control, cataloging systems maintain an authority record for a person, body, work, or subject, and route transliterations, pseudonyms, and translated forms to it, so two catalogers entering different forms still link to the same entity. In web canonicalization, redirect rules and canonical tags route every variant address (with or without trailing slash, secure or not, with or without tracking parameters) to one canonical address, so ranking accrues to the canonical while users still reach the page by any variant. In master data management, a customer-record system routes every variant capture of a person to one master identity, so that history, contacts, and compliance checks aggregate correctly across channels. In bioinformatics, registries maintain a canonical symbol while routing legacy aliases to it, without which cross-study meta-analyses would double-count. In package registries, old names redirect to new ones after a rename or fork, so existing imports still resolve. In network naming, an alias record points one hostname through to an authoritative one. And in legal identity, known aliases all route to one master record so that warrants, priors, and case histories aggregate against the master rather than fragmenting across surface names.

Clarity

The diagnostic is sharp because two tests separate alias-to-authority from look-alikes. The aggregation test: if two users find the referent through two different labels, do their interactions — citations, purchases, contacts, links — accrue to the same identity? If yes, an alias-to-authority layer is in operation; if no, the labels are separate identities or a flat synonym list. The maintenance test: when one label changes — a person renamed, an address moved, a symbol officially revised — is there a defined operation that updates the authority and leaves the variant routing intact? If yes, the asymmetry is real; if no, it is just a tagging convention. When both tests pass, the pattern is operative regardless of substrate. The tests also make the pattern's absence diagnosable: a record system with a "preferred name" field but no master identity is not alias-to-authority but a label preference on a fragmented identity; a retrieval system that treats every address variant as a separate resource is not canonicalizing but fragmenting. Naming the pattern thus turns a vague worry about duplicate or fragmented records into a precise question about whether the aggregation and maintenance properties actually hold.

Manages Complexity

The pattern concentrates identity-bookkeeping into one place. Without it, every component that touches a referent must be aware of every name the referent has ever had, and updates must be propagated everywhere. With it, components reference the authority form, typically through the resolution function, and the alias mapping absorbs all the historical, multilingual, typographic, and political variation in surface labels. The variant set can grow without bound without changing how anything downstream counts, links, or aggregates, because the proliferation is confined to one layer whose only job is to route. The pattern also makes the cost of not canonicalizing visible and measurable: a record-linkage failure rate, a duplicate count, a fragmented index — each is the negative space where alias-to-authority should have been and was not. By localizing identity to a single authoritative form and pushing all surface variation into a routing layer, the pattern keeps the combinatorial growth of labels from leaking into the downstream systems that depend on stable identity, so that those systems see one referent no matter how many ways the world has found to name it.

Abstract Reasoning

The role-set lets a reasoner compare an authority file, a name-routing table, a symbol registry, a customer master, and address canonicalization and see the same skeleton: many surface labels, one designated authority, a routing function, an asymmetric maintenance contract, and an aggregation property on which downstream counting depends. Recognizing the shared skeleton supports inference and lets techniques borrow across substrates. The web world's discipline around permanent versus temporary routing, preserving accrued ranking through redirects, and avoiding routing chains transfers directly to authority-file migrations and to version-deprecation strategy, because the structural questions are identical: how to keep old links resolving while updating the underlying authority, and how to prevent the alias layer from itself becoming a source of identity drift. The pattern also supports a lifecycle inference: a relabeling event is a controlled promotion of a variant to authority and demotion of the prior authority to alias, which must be performed without breaking variant routing — and recognizing this as a structural operation, rather than an ad-hoc rename, is what keeps the aggregation property intact across the change. The asymmetry is the invariant that all this reasoning turns on; lose it, and the mapping collapses into a synonym list with no identity to aggregate to.

Knowledge Transfer

Once a reader internalizes the asymmetry — one authority, many aliases, routed many-to-one — they recognize the pattern across domains and, equally, recognize what is missing when a system claims to handle aliases but does not. The transfer is prescriptive: when a system accumulates many ways to refer to the same thing and downstream uses start fragmenting, the fix has a name and a known shape. The disciplines port directly across substrates because they address the same four roles. The redirect-hygiene practices of web canonicalization — permanent versus temporary, ranking preservation, chain avoidance — transfer to authority-file migration and to package-name deprecation, where the same failure (a broken or chained route losing accrued identity) recurs in identical form. The master-data discipline of routing every capture to one identity transfers to scholarly author disambiguation and to legal alias management, where its absence produces the same fragmentation — five records masquerading as five entities. The deepest carry is the recognition that the maintenance contract is the load-bearing commitment: a practitioner who has watched an authority file keep dozens of transliterated and translated forms resolving to one author carries directly into keeping legacy gene aliases, former customer names, or deprecated package names resolving to their canonical forms, because in every case the structure that must hold — one fixed authority, an explicit route from each variant, and a contract that new variants are added rather than promoted — is the same, and so is the cost of letting it lapse: identity that fragments silently across the very labels the pattern exists to unify.

Examples

Formal/abstract

Web URL canonicalization is the pattern in its most mechanically precise form. A single page is reachable through many surface addresses — http and https, with and without a trailing slash, with and without www, with assorted tracking query parameters. The authority form is the one canonical URL deliberately fixed as the page's identity for indexing and ranking; the variant set is every other reachable address; the resolution function is the combination of permanent (301) redirects and rel="canonical" tags that routes any variant request to the canonical; and the stability contract is the commitment that the canonical outlives the variants and that newly discovered variants are added to the redirect map rather than promoted to new pages. The many-to-one asymmetry is load-bearing and operationally consequential: link equity and ranking accrue to the canonical, not to the variant the user happened to follow, while the user still reaches the page by any address. The two confirming tests are concrete. The aggregation test: do inbound links via different variants accrue to one ranked identity? If yes, canonicalization is operative; if the search index treats each variant as a separate resource, the system is fragmenting, splitting ranking across duplicates. The maintenance test: when the canonical changes, is there a defined operation (update the redirects, repoint the canonical tag) that preserves variant routing? The web discipline the prime names — permanent versus temporary routing, preserving accrued ranking through redirects, avoiding redirect chains — is exactly the apparatus that keeps the asymmetry intact, and a broken or chained redirect is the characteristic failure: accrued identity lost because a variant stopped routing to its authority.

Mapped back: URL canonicalization instantiates all four roles — canonical URL, variant addresses, redirect/canonical-tag resolution, stability contract — and the many-to-one asymmetry is what lets ranking aggregate to one identity while the page stays reachable by any address, with redirect hygiene the discipline that protects it.

Applied/industry

Two cases run the identical one-authority-many-aliases structure on substrates the web shares no machinery with. In library and archival authority control, a cataloging system maintains an authority record for a person and routes every variant form — transliterations, pseudonyms, married and maiden names, translated forms — many-to-one to it. The authority form is the established heading; the variant set is the cross-reference forms; the resolution function is the syndetic structure that sends a searcher from any variant to the authorized entry; and the stability contract is the commitment to add newly discovered variants as cross-references rather than create competing records. The aggregation property is the whole point: two catalogers entering different forms of a name link to the same entity, so a search on any variant retrieves the author's complete output — and its absence is the fragmentation failure where five transliterations masquerade as five authors. In bioinformatics, a gene-symbol registry maintains one canonical symbol while routing legacy aliases and superseded symbols to it; the stability contract — old symbols are kept as aliases that resolve, never silently promoted to new canonicals — is what lets a cross-study meta-analysis aggregate measurements that different papers labeled with different historical symbols. Without it, the same gene under two aliases is double-counted, the precise pathology the asymmetry prevents. The maintenance contract is load-bearing in both: a controlled relabeling (promoting a variant to authority and demoting the prior authority to alias) must be performed without breaking variant routing, or accrued identity fragments. A practitioner who has watched an authority file keep dozens of name forms resolving to one author carries directly into keeping legacy gene aliases resolving to one canonical symbol, because the structure that must hold — one fixed authority, an explicit route from each variant, a contract that new variants are added not promoted — is identical.

Mapped back: Library authority control and gene-symbol registries span cataloging and genomics; in each, many surface labels route many-to-one to one authority so that identity aggregates correctly, and the maintenance contract is the load-bearing commitment whose lapse fragments identity across the very labels the pattern unifies.

Structural Tensions

T1 — Asymmetric Authority versus Flat Synonymy (sign/direction). The load-bearing feature is that one form is privileged and the rest route to it; lose the asymmetry and the mapping collapses into a peer synonym list with no identity to aggregate to. The two are constantly conflated. The failure mode is treating variants as peers, so counting, citation, and ownership fragment across labels because no single form is the identity. Diagnostic: ask which one form appears in counts and which the system commits to maintaining; if any member can stand for the group, this is synonymy, and the aggregation property the prime depends on does not hold.

T2 — Canonical Choice versus Contested Authority (scopal). The authority form is "often arbitrary among the variants but deliberately fixed" — but in many domains which variant deserves to be canonical is contested (whose transliteration, which jurisdiction's legal name, which fork's package name). The arbitrariness is real but the choice carries operational and political weight. The failure mode is a canonical form that one constituency rejects, so they maintain a competing authority and the referent re-fragments. Diagnostic: ask whether all parties route to the same authority or whether rival canonicals exist; competing authority forms are two mappings, not one, and reproduce the fragmentation the pattern exists to cure.

T3 — One Authority versus Genuine Split (coupling). The pattern presumes the variants really denote one referent — but identity resolution is fallible, and a mapping can over-merge, routing variants of two distinct referents to one authority. The asymmetry then aggregates things that should stay apart. The failure mode is a conflation: two people, two genes, two customers collapsed into one identity because their labels were wrongly mapped together. Diagnostic: periodically test whether the variants under one authority truly co-refer; the aggregation property is a benefit only when the merge is correct, and an over-merge is harder to detect than a fragmentation because everything resolves cleanly.

T4 — Stability Contract versus Necessary Relabeling (temporal). The contract says the authority outlives the variants and new variants are added rather than promoted — but sometimes the authority genuinely must change (a rename, a fork, an official revision), requiring a controlled promotion of a variant to authority. The contract resists exactly the change that is occasionally correct. The failure mode is either an ossified authority kept past its validity, or an ad-hoc rename that breaks variant routing and loses accrued identity. Diagnostic: ask whether relabeling is performed as a structured promote-and-demote that preserves routing, or as an overwrite; only the former honors both the stability contract and the occasional need to move the authority.

T5 — Routing Chains versus Direct Resolution (coupling). Resolution must route each variant to the authority, but as authorities themselves get relabeled, variants can come to point at a former authority that now points at the current one, building chains. Each hop is a place the route can break. The failure mode is a variant that resolves through several stale authorities until a broken link loses it, so accrued identity silently detaches. Diagnostic: check whether variants resolve directly to the current authority or through chains of superseded ones; redirect hygiene (flatten chains, repoint variants to the live authority) is what keeps the resolution function from decaying into a fragile pointer trail.

T6 — Confined Variation versus Variant-Layer Drift (scalar, local vs global). The pattern's payoff is confining all surface variation to one routing layer so downstream systems see one stable identity — but that layer can itself become a source of drift if variants are added inconsistently or with their own sub-aliases. The thing meant to absorb proliferation starts generating it. The failure mode is an alias layer so tangled that it no longer reliably routes, reintroducing at the routing layer the fragmentation it was built to prevent. Diagnostic: ask whether the variant set is flat (every variant routes directly to the authority) or has grown internal structure; a routing layer that needs its own canonicalization has stopped being the solution and become a second instance of the problem.

Structural–Framed Character

Alias-to-authority mapping sits near the structural pole of the structural–framed spectrum, at an aggregate of 0.2. Its core is a relational pattern that travels — one canonical authority form, a variant set, a resolution function routing every variant many-to-one to it, and a stability contract — and its load-bearing feature, the asymmetry that privileges exactly one form as the identity, is purely structural.

Three diagnostics read fully structural. The pattern carries no home vocabulary that must travel with it: the same asymmetric many-to-one routing describes library authority control, web URL canonicalization, master-data management, bioinformatics gene aliases, DNS CNAMEs, and legal aliases, each in its own field's terms, so vocab_travels is 0. It carries no inherent approval or disapproval — choosing one form as canonical is an operational, value-neutral act — so evaluative_weight is 0. And invoking it RECOGNIZES a routing asymmetry already present in the system (one form privileged, the rest reachable surfaces) rather than importing an interpretive frame, so import_vs_recognize is 0.

The two half-marks, institutional_origin (0.5) and human_practice_bound (0.5), reflect the prime's origin in cataloging and master-data practice, where a curator deliberately fixes the authority form. But that institutional flavor is held off the full mark by genuinely non-curated instances: a DNS CNAME routes aliases to a canonical name by protocol, and gene aliases resolve to a reference symbol through automated mapping, neither requiring a human institution to constitute the asymmetry. Those mechanisms show the core routing structure extending beyond human-only practice, which is why both criteria sit at 0.5. The structural label is well earned; the cataloging origin is a tint, not the substance.

Substrate Independence

Alias-to-authority mapping is a strongly substrate-independent prime — composite 4 / 5 on the substrate-independence scale. Its four-role skeleton — an authority form, a variant set, a resolution function, and a stability contract, held together by the many-to-one asymmetry that makes identity aggregate — is stated in purely relational terms and recognized rather than translated wherever it appears, which sustains the structural-abstraction mark. The domain breadth is wide and genuinely cross-substrate: the same asymmetric many-to-one routing recurs in library and archival authority control, web URL canonicalization (redirects and canonical tags), master-data and customer-identity management, bioinformatics gene-symbol registries, package-name redirection, DNS CNAME records, and legal alias management. Transfer evidence is concrete: URL canonicalization, library authority control, and gene-symbol registries share the same aggregation and maintenance tests and the same controlled promote-and-demote relabeling, and redirect-hygiene disciplines port directly from the web to authority-file migration and package-name deprecation. What holds it at 4 rather than 5 is a real institutional flavor from its cataloging and master-data origins, where a curator deliberately fixes the authority form — but that lean is held in check by genuinely non-curated instances (a DNS CNAME routing aliases by protocol, gene aliases resolving through automated mapping) where the asymmetry is constituted without any human institution, showing the core routing structure extends beyond human-only practice.

  • Composite substrate independence — 4 / 5
  • Domain breadth — 4 / 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.Alias-to-AuthorityMappingcomposition: IndirectionIndirection

Parents (1) — more general patterns this builds on

  • Alias-to-Authority Mapping presupposes Indirection

    The file: alias-to-authority IS implemented through indirection (a resolution layer routes a variant to its authority) but is the SPECIFIC asymmetric, many-to-one, identity-aggregating use of it. Indirection is the generic mechanism; the aggregation-bearing many-to-one asymmetry is the specialization. Presupposes indirection.

Path to root: Alias-to-Authority Mapping → Indirection → Layering

Neighborhood in Abstraction Space

Alias-to-Authority Mapping sits in a moderately populated region (42nd percentile for distinctiveness): it has near-neighbors but no dense thicket of synonyms.

Family — Mappings, Functions & Equivalence (10 primes)

Nearest neighbors

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

Not to Be Confused With

The embedding-nearest neighbor, access_control (similarity 0.88), is a confusion driven almost entirely by the "access point" surface of the name rather than by any structural kinship. Access control answers who is permitted to reach or operate on a resource — it is about authorization, permission, gatekeeping. Alias-to-authority mapping answers by which names a resource can be reached, and which of those names is its identity — it is about routing labels to a canonical referent so that interactions aggregate. The two operate on orthogonal questions: one could have a perfectly canonicalized authority record with no access control at all (every name routes to it, anyone may reach it), or strict access control over a fragmented identity (tightly permissioned, but the same entity scattered across unmapped labels). Conflating them leads a designer to think that controlling access has solved identity (it has not — the aliases may still fragment) or that canonicalizing names has controlled access (it has not — routing is not permission). The discipline is to keep the permission question and the naming question entirely separate.

A more substantive confusion is with bare indirection. Alias-to-authority is implemented through indirection — a resolution layer routes a variant to its authority, exactly as a pointer routes to its target. But indirection is the generic mechanism, while alias-to-authority is a specific asymmetric, many-to-one, identity-aggregating use of it. Plain indirection need not be asymmetric (two-way pointers, symmetric links), need not aggregate identity (a redirect can simply forward without any notion of a privileged canonical form), and need not carry a stability contract. The load-bearing addition is the many-to-one asymmetry that makes exactly one form the identity for counting, deduplication, and ownership, with the rest as reachable surfaces. A practitioner who sees only "this is indirection" misses what distinguishes the pattern — that the routing direction carries operational consequences (which name appears in counts, which gets cited, which the system maintains) and that the aggregation property depends on the asymmetry. Treating alias-to-authority as mere indirection invites the flat-synonym collapse of tension T1, where labels become peers and identity has nothing to aggregate to.

A third confusion is with versioning, which arises because both manage multiplicity around a thing's identity and both involve "old" and "current" forms. The distinction is the axis of multiplicity. Versioning arranges the successive temporal states of one evolving artifact — v1, v2, v3 — and its question is "which state, and in what order?" Alias-to-authority arranges the coexisting surface labels of one referent at a point in time — spellings, translations, former names — and its question is "which of these names is the identity, and how do the rest route to it?" The two interact (a relabeling event, tension T4, looks superficially like a version bump), but they fail differently and prescribe different machinery: versioning needs ordered history and state reconstruction, while alias-to-authority needs a fixed canonical form and a flat routing layer. Confusing them leads a designer to model coexisting name variants as a version chain (imposing a spurious temporal order on labels that are simultaneous) or to model genuine state succession as aliasing (losing the ordered history that versioning would preserve).

These distinctions matter because each protects a different feature of the prime. Holding alias-to-authority apart from access_control keeps the naming/routing question separate from the permission question. Holding it apart from bare indirection preserves the many-to-one asymmetry and aggregation property that are the whole point, rather than reducing it to a generic pointer. And holding it apart from versioning keeps the coexisting-labels axis distinct from the temporal-succession axis, so neither is modeled with the other's machinery. In every case the discriminator is the same: exactly one privileged authority form, with every variant routing to it, so that identity aggregates.

Solution Archetypes

No catalogued solution archetypes reference this prime yet.