Skip to content

Identity-Providing Kind

Prime #
906
Origin domain
Philosophy
Subdomain
metaphysics of kinds and sortals → Philosophy

Core Idea

An identity-providing kind is a category whose membership fixes what it takes for an instance to be the same instance over time — it supplies the persistence criteria the instance lives by, not merely a description the instance satisfies for a while. To say that some category is identity-providing for a particular thing is to say that the thing belongs to that category for as long as it exists, and that what counts as "the same one across time" is set by what it is to be a member of that category. A phase category, by contrast, holds only for an interval — ceasing to fall under it is not ceasing to exist — and a role category is a position the same thing occupies temporarily without the role supplying its persistence. The structural commitments are four: for every instance there is some identity-providing category (the instance does not hang in mid-air); for each candidate category one can ask whether ceasing to fall under it is ceasing to exist; categories that fail that test are roles or phases, real and predicable but not the source of persistence criteria; and categories that pass it confer their persistence-relevant properties on their instances.

The pattern is what lets ordinary reference and tracking work at all. When someone picks out "the same one that was here yesterday," the implicit identity-providing kind is the underlying kind, not the heterogeneous bundle of roles the instance happens to occupy. Without an identity-providing kind, persistence questions — "is this still the same thing?" — have no answer, because there is no criterion against which to settle them. The decisive move is the cease-to-exist test: it converts a metaphysical question into an operational one that travels across substrates, distinguishing what a thing is from what it merely does or is, for now.

How would you explain it like I'm…

Always a Dog

A puppy can be a 'puppy' for a while, then grow up and stop being a puppy — but it's still the same dog the whole time. Being a puppy is just a stage. Being a DOG is different: it's a dog from start to finish, and 'is it still the same dog?' is answered by it being a dog. The kind of thing that something stays for its whole life, that tells you it's still the same one, is its identity-providing kind.

Stage Versus What-It-Is

Some categories a thing only belongs to for a while: 'toddler,' 'student,' 'champion.' Stopping being a toddler doesn't mean you stopped existing — those are stages or roles. But there's usually one deeper category a thing belongs to for its ENTIRE existence, and that category is what decides whether it's 'the same one' over time. For you, 'human being' might be that category; for a particular tree, 'oak.' The test is simple: if the thing stopped fitting the category, would it cease to EXIST, or just change? If ceasing to fit means ceasing to exist, that category is identity-providing; if not, it's just a role or a phase.

The Cease-to-Exist Test

An identity-providing kind is a category whose membership fixes what it takes for an instance to be the SAME instance over time — it supplies the persistence criteria the thing lives by, not just a description it happens to fit for a while. Saying a category is identity-providing for some thing means the thing belongs to it for as long as it exists, and 'the same one across time' is set by what membership in that category requires. Contrast a phase category, which holds only for an interval (leaving it isn't ceasing to exist), and a role category, a position the same thing occupies temporarily without that role supplying persistence. The structural test is the cease-to-exist test: ask whether ceasing to fall under the category would be ceasing to exist. Categories that pass confer their persistence-relevant properties on their instances; categories that fail are real and predicable but are only roles or phases. This is what lets ordinary tracking work: when you pick out 'the same one that was here yesterday,' the implicit kind is the underlying one, not the bundle of temporary roles.

 

An identity-providing kind is a category whose membership fixes what it takes for an instance to be the same instance over time — it supplies the persistence criteria the instance lives by, not merely a description the instance satisfies for a while. To say some category is identity-providing for a particular thing is to say the thing belongs to it for as long as it exists, and that what counts as 'the same one across time' is set by what it is to be a member of that category. A phase category, by contrast, holds only for an interval — ceasing to fall under it is not ceasing to exist — and a role category is a position the same thing occupies temporarily without the role supplying persistence. Four structural commitments: for every instance there is some identity-providing category (the instance does not hang in mid-air); for each candidate category one can ask whether ceasing to fall under it is ceasing to exist; categories that fail that test are roles or phases, real and predicable but not the source of persistence criteria; and categories that pass it confer their persistence-relevant properties on their instances. The pattern is what lets ordinary reference and tracking work at all — when someone picks out 'the same one that was here yesterday,' the implicit identity-providing kind is the underlying kind, not the heterogeneous bundle of roles the instance happens to occupy. Without one, persistence questions ('is this still the same thing?') have no answer, since there is no criterion to settle them against. The decisive move is the cease-to-exist test, which converts a metaphysical question into an operational one that travels across substrates, distinguishing what a thing is from what it merely does or is, for now.

Structural Signature

the instance to be tracked — the candidate category — the cease-to-exist test — the identity-providing kind that supplies persistence criteria — the role/phase categories that do not — the exactly-one-bearer-of-persistence invariant

The pattern is present when each of the following holds:

  • An instance. Some particular thing is to be tracked across change; it does not hang in mid-air — there is some category that is identity-providing for it.
  • A candidate category. For any category the instance satisfies, one can ask the diagnostic question: is it identity-providing, a role, or a phase?
  • The cease-to-exist test. The operational discriminator: does the instance cease to exist when it stops falling under the category? If yes, the category is identity-providing for it; if no, the category is a role (a position occupied temporarily) or a phase (an interval the instance passes through without becoming numerically different).
  • The identity-providing kind. The category that passes the test fixes what it takes for the instance to remain the same instance over time — it supplies persistence criteria, not a temporary description, and confers its persistence-relevant properties on its instances.
  • The role/phase categories. Categories that fail the test are real and predicable but do not supply persistence; they attach to and detach from the instance without threatening its identity.
  • The single-bearer invariant. Exactly one category bears persistence criteria; all others are predicates the same entity can gain and lose. Only changes to the identity-providing kind threaten identity; everything else is property change on a persisting entity.

The cease-to-exist test is substrate-neutral, applying identically to persons, organisms, classes, and corporate persons. Its characteristic failure — modeling a role or status as the identity-providing kind — predicts a determinate absurdity: the instance vanishes when the status ends.

What It Is Not

  • Not institution. An institution is a durable rule-system that may confer identity-providing status on entities (legal personhood, corporate continuity); the identity-providing kind is the category that supplies persistence criteria to an instance. The institution can be the source of the criterion, but the prime is the criterion-bearing category, not the rule-system.
  • Not a role. A role is a position an instance occupies temporarily, failing the cease-to-exist test; the identity-providing kind is precisely the category an instance cannot survive losing. Roles attach and detach; the kind is what persists underneath them.
  • Not scaffolding. Scaffolding is temporary support removed once a structure stands; the identity-providing kind is permanent for the instance's whole existence. One is provisional by design; the other is load-bearing for as long as the thing exists.
  • Not ontology. An ontology is a whole specification of categories and relations; the identity-providing kind is one specific meta-property within such a specification — the question of which category among many supplies persistence. The ontology is the map; the prime is one load-bearing distinction on it.
  • Not classification. Classification assigns an instance to categories it satisfies; identity-providing kind asks the prior question of which satisfied category supplies persistence criteria. A classifier sorts; it does not adjudicate persistence.
  • Not essentialism in general. Essentialism names necessary defining properties broadly; the identity-providing kind isolates the one essentialist sub-question — which category fixes sameness over time — and supplies the cease-to-exist test the broad notion lacks. Not every essential property is identity-providing.
  • Common misclassification. Typing an entity by its current salient status. The catch is the cease-to-exist test: if losing the category leaves a surviving entity (graduation, account deactivation, leaving office), the category is a role and must not be the identity-providing kind — modeling it as such makes the instance vanish when the status ends.

Broad Use

The pattern recurs wherever instances are tracked across change. In commonsense modeling and natural language, speakers routinely treat an underlying kind as identity-providing and a current occupation as a phase. In conceptual modeling and ontology engineering, the distinction is operationalized as a meta-property that marks the category supplying persistence criteria and contrasts it with those that do not, and large ontology projects use it to detect category-design errors at scale. In social systems and role theory, distinguishing the person from the office they hold — the holder from the holdership — is what makes succession, term limits, and removal intelligible. In biological taxonomy, the kind is identity-providing for the organism across its developmental stages, which are phases rather than kinds the same organism switches into and out of by becoming numerically different. In object-oriented design and type systems, the distinction between a class an instance belongs to for life and a state or role it occupies temporarily maps directly onto the pattern, and the classic design failures are exactly the cases where a role is mistakenly modeled as the identity-providing kind. In law, a natural person is identity-providing across every role they occupy, and an incorporated body is identity-providing across changes of officers, address, and even name.

Clarity

The pattern is sharp because there is a single operational test: does the instance cease to exist when it stops falling under the category? If yes, the category is identity-providing for it; if no, the category is a role or a phase. The test is substrate-independent — a philosopher applies it to persons, a biologist to organisms, a modeler to a class, a lawyer to corporate personhood, all with the same logic — and its failures are recognizable as design errors of a predictable kind. Modeling a temporary status as the identity-providing kind predicts absurdities: that an instance ceases to exist when the status ends, that ending a relationship annihilates one of its parties, that an office-holder and the human are one entity with the consequence that the human pre-dates their own existence or vanishes on leaving the post. Naming the pattern thus locates a whole class of modeling bugs precisely, as violations of the cease-to-exist test, rather than leaving them as vague intuitions that "something is off" with the category structure.

Manages Complexity

Real entities sit at the intersection of many categories. Without the distinction between identity-providing kinds and role-or-phase categories, every change of category looks like a change of entity, and tracking becomes impossible: each new status would spawn a new thing, and the linkage between past and present would dissolve. By naming exactly one category as the bearer of persistence criteria and treating the rest as predicates the same entity can gain and lose, the pattern reduces the bookkeeping load to a single load-bearing relation. Only changes to the identity-providing kind threaten identity; everything else is property change on a persisting entity. This is what licenses a system to carry one stable handle for an evolving thing while letting an unbounded set of roles, statuses, and phases attach to and detach from it — the customer who becomes an ex-customer, the patient who is discharged, the cub who matures — without ever losing the thread that they are the same one throughout. The complexity that would otherwise come from treating every status transition as a new entity is absorbed once the identity-providing kind is fixed.

Abstract Reasoning

Identity-providing kind sits within a family of metaphysics-of-kinds distinctions and sharpens the broader notion of essential property to a specific sub-pattern. Where essentialism names inherent defining properties in general, this pattern isolates the one essentialist sub-question that supplies persistence criteria — and it comes with an operational test that the broader notion lacks. The cease-to-exist test is one face of rigidity: an identity-providing kind necessarily applies for as long as the instance exists, where a role does not. Reasoning with the pattern proceeds by interrogating, for a given instance, which category it belongs to for as long as it exists, which it occupies only for a phase, and whether a proposed modeling of some category as identity-providing produces absurd consequences under the test. This explains why some essentialist intuitions are robust — the kind genuinely is identity-providing — while others are mistaken, treating what is in fact a role as though it supplied identity. It also separates the pattern cleanly from mere classification (which assigns an instance to categories) and from set membership (the extensional view), both of which leave the prior question untouched: among the categories an instance satisfies, which one supplies its persistence criteria?

Knowledge Transfer

The diagnostic transfers across philosophy, biology, ontology engineering, programming, organizational theory, and law because it interrogates persistence rather than any domain's machinery. For a given instance: what category does it belong to for as long as it exists; what categories does it occupy only for a phase; and if some candidate is modeled as the identity-providing kind, does the cease-to-exist test yield absurdity? A software architect modeling a person with a mutable role-set, a lawyer distinguishing the natural person from the business entity they own, and a biologist tracking an organism across metamorphosis are performing the identical reasoning, and they avert the identical bug. The canonical transferable failure is concrete: a system that makes a relationship-status the identity-providing class and then loses an entity's data when the status ends — deactivating an account and finding the person gone — has committed the same error whether the substrate is a customer database, a healthcare record, a legal case file, or a demographic register, because in each the underlying kind (the person, the party) was the true bearer of identity and the status was only a role. A practitioner who has diagnosed the error once in code carries the cease-to-exist test directly into modeling patients-versus-persons, employees-versus-people, or defendants-versus-persons, because the structural relation between kind and instance is the same everywhere and the failure mode — role mistaken for kind — recurs in identical shape. The deepest carry is that persistence is a question to be answered explicitly, by naming which category an instance cannot survive losing, and that this single question disciplines category design across every substrate where things are tracked through change.

Examples

Formal/abstract

The sortal tradition in metaphysics gives the pattern its sharpest formal worked instance through the contrast between a substance-sortal and a phase-sortal. Take a particular person. Several categories apply to them at once: human being, child, student, employee, taxpayer. The cease-to-exist test discriminates among them. Does the instance cease to exist when it stops being a child? No — the same person continues as an adult, so child is a phase, an interval the instance passes through without becoming numerically different. Does it cease to exist when it stops being a student or an employee? No — these are roles, positions occupied temporarily. Does it cease to exist when it stops being a human being? Yes — there is no surviving entity, so human being is the identity-providing kind, the single category bearing the persistence criteria the instance lives by. The single-bearer invariant is on display: exactly one of the many satisfied categories supplies persistence, and all the rest are predicates the same entity gains and loses. The characteristic failure is concrete and predictable — model a role as the identity-providing kind and the test yields absurdity: if student were identity-providing, graduation would annihilate the person and a numerically new entity would begin, severing the link between the undergraduate and the alumnus. This is exactly the diagnostic OntoClean operationalizes as the rigidity meta-property: a category that necessarily applies for as long as the instance exists (+I/+R) versus one that attaches and detaches (-R), with category-design errors detected at scale as rigidity violations.

Mapped back: The substance-sortal/phase-sortal contrast instantiates the prime's roles — instance, candidate categories, cease-to-exist test, the one identity-providing kind, the role/phase remainder — and the single-bearer invariant is what blocks the absurdity of an instance vanishing when a role ends.

Applied/industry

Two engineering and institutional cases run the identical cease-to-exist test on substrates a person shares no metaphysics with. In object-oriented software design, the classic modeling bug is mistaking a role for the identity-providing class. Suppose a system models a person by subclassing Customer and Employee directly from Person, making the role the type. The cease-to-exist test predicts the failure: when a customer relationship ends, the design implies the person ceases to exist, so deactivating the account loses the human's data — the same person, now needed as an employee or a re-acquired customer, is gone. The fix the prime prescribes is to make the underlying kind (Person) identity-providing and model Customer and Employee as roles the same persisting instance gains and loses — a mutable role-set on a stable identity, which is exactly the pattern mature domain models converge on. In law, the corporation is the institutional case: an incorporated body is identity-providing across changes of officers, registered address, and even legal name. The cease-to-exist test settles succession and continuity questions — replacing the entire board does not end the corporation, because officer is a role and corporation is the identity-providing kind, so contracts, liabilities, and the legal personality persist across the turnover. A legal regime that treated the office-holder and the legal person as one entity would imply the absurdity the prime names: that the human pre-dates their own existence or vanishes on leaving the post. The same canonical bug — role mistaken for kind, data or continuity lost when the status ends — recurs whether the substrate is a customer database, a healthcare record (patient-versus-person), or a corporate registry, and the cease-to-exist test averts it identically.

Mapped back: The role-modeled-as-class bug and corporate continuity span software and law; in each, naming the underlying kind (person, corporation) as the single bearer of persistence and demoting statuses to roles is what prevents the entity from vanishing when a status ends — the prime's characteristic failure averted by its characteristic test.

Structural Tensions

T1 — Role Mistaken for Kind (sign/direction). The single defining failure is modeling a role or status as the identity-providing kind, so the instance vanishes when the status ends — deactivating an account loses the person. The cease-to-exist test is the guard, but the pull toward typing entities by their current salient role is strong. The failure mode is data loss or broken continuity on status transition. Diagnostic: for the proposed type, ask whether the instance ceases to exist when it stops falling under it; if losing the category leaves a surviving entity, it is a role and must not be the type.

T2 — Exactly One Bearer versus Multiple Candidates (scopal). The invariant says exactly one category supplies persistence — but for some entities the choice among candidates is genuinely contested: is a ship its hull-kind or its function-kind, is a reformed institution the same one? When two categories both seem to pass the cease-to-exist test, the single-bearer assumption is strained. The failure mode is arguing past each other because each party fixed a different identity-providing kind. Diagnostic: where two candidates both seem load-bearing, look for a case that splits them (the entity persists through one but not the other); if none exists, the identity criterion is underdetermined and must be stipulated, not discovered.

T3 — Persistence Criteria versus Gradual Replacement (temporal). The kind fixes what it takes to remain the same instance, but it does not by itself resolve sorites-style gradual replacement — the ship whose planks are swapped one by one, the organization wholly turned over. The kind says "same human persists," yet says little about how much change the criterion tolerates. The failure mode is assuming the identity-providing kind settles every persistence question when it leaves the threshold of allowable change open. Diagnostic: ask whether the kind's persistence criterion specifies a tolerance for incremental change; if it only names the category, borderline continuity cases remain genuinely open under it.

T4 — Sortal Realism versus Modeling Convention (scopal). The prime can be read as discovering a real metaphysical fact (the kind that nature makes identity-providing) or as a modeling choice (the category the system elects to track identity by). For natural kinds the first reading fits; for legal and software entities, identity-provision is stipulated. The failure mode is treating a chosen convention as a discovered necessity, so a defensible alternative modeling looks like an error. Diagnostic: ask whether anything outside the system's conventions fixes the identity-providing kind; where personhood or entity-continuity is conferred by rule, the kind is designed, and disputes about it are about what to stipulate.

T5 — Identity-Providing Kind versus Essential Property (coupling). The prime sharpens essentialism to the one sub-question of persistence, but the boundary with general essential-property reasoning blurs: not every essential property is identity-providing, and not every identity-providing kind exhausts an entity's essence. The failure mode is sliding from "this property is essential" to "this property fixes identity over time," importing persistence consequences a mere essential property does not carry. Diagnostic: ask specifically whether losing the property ends the entity's existence, not merely whether the property is necessary; rigidity-over-time is narrower than essentiality, and only it supplies persistence criteria.

T6 — Kind-Change versus Entity-Change (temporal). The framework says only changes to the identity-providing kind threaten identity — but some transformations genuinely change an instance's kind (a caterpillar to a butterfly read as one organism, a startup to a public company). Whether such a transition is a phase of one continuant or the end of one entity and start of another is exactly what the kind is supposed to settle, yet metamorphic cases push on it. The failure mode is forcing a true kind-transition into the phase mold (or vice versa), mis-tracking identity across the boundary. Diagnostic: ask whether the developmental program treats the stages as one continuant by design; metamorphosis is a phase only if the kind's persistence criteria explicitly span the transformation.

Structural–Framed Character

The identity-providing kind sits near the structural pole of the structural–framed spectrum, at an aggregate of 0.2. At bottom it is a bare metaphysical pattern — the sortal that supplies an instance's persistence criteria, separated by the cease-to-exist test from roles and phases that an instance merely occupies for a while — and it transfers cleanly across biology, code, and law.

Three diagnostics read fully structural. The pattern carries no inherent approval or disapproval — that organism is identity-providing for a living thing is a neutral persistence fact — so evaluative_weight is 0. Its origin is not institutional in general: human being is identity-providing for a person, organism for a living thing, by nature rather than by decree, so institutional_origin is 0. And it requires no human practice to obtain — the persistence criteria of a biological kind hold whether or not anyone tracks them — so human_practice_bound is 0.

The two half-marks are vocab_travels (0.5) and import_vs_recognize (0.5), and both reflect the same thing: a faint philosophical-vocabulary flavor. The prime's home idiom — sortal, persistence criterion, qua, OntoClean's +I/−I — is technical, so a little of that lexicon tends to travel with the pattern, and invoking it carries a mild whiff of importing the metaphysician's frame. But the cease-to-exist test cuts through that: it converts the metaphysical question into an operational one — does ceasing to fall under this category mean ceasing to exist? — that any substrate can answer for itself, which is exactly why the prime applies as readily to a software class-versus-state distinction or legal personhood as to natural kinds. The structural label is correct; the philosophical vocabulary is a tint, not the substance.

Substrate Independence

Identity-providing kind is about as substrate-independent as a prime can be — composite 5 / 5 on the substrate-independence scale. Its signature is a bare metaphysical pattern — the single category that supplies an instance's persistence criteria, separated by the cease-to-exist test from the roles and phases an instance merely occupies for a while — and that test is medium-neutral, converting a metaphysical question into an operational one any substrate can answer for itself, which earns the maximal structural-abstraction mark. The domain breadth is maximal: the same persistence-criterion question runs identically through the philosophical sortal tradition (Wiggins, Lowe, Strawson), ontology engineering (OntoClean's rigidity / +I meta-property), social role theory (the office-holder versus the office), biological taxonomy (the organism across its developmental phases), object-oriented design and type systems (class-for-life versus temporary state or role), and law (the natural and corporate person across changes of role, address, and name). Transfer evidence is strong though slightly less than maximal at 4: the substance-sortal/phase-sortal contrast, the role-modeled-as-class software bug, and corporate continuity demonstrably share the same cease-to-exist test and the same role-mistaken-for-kind failure mode, with the test averting the identical vanishing-instance bug across code, law, and metaphysics. Because the pattern carries no evaluative or institutional load — human being is identity-providing for a person and organism for a living thing by nature, not by decree — every component reads at or near the ceiling, making this one of the catalog's canonical 5s.

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

Relationships to Other Primes

One-hop neighborhood: parents above, mutual partners to the right, children below.Identity-ProvidingKindsubsumption: EssentialismEssentialismsubsumption: Criteria of IndividuationCriteria ofIndividuation

Parents (2) — more general patterns this builds on

  • Identity-Providing Kind is a kind of Criteria of Individuation

    child of emergent criteria_of_individuation

  • Identity-Providing Kind is a kind of, typical Essentialism

    The file: identity_providing_kind ISOLATES the one essentialist sub-question (which category fixes sameness over time) and supplies the cease-to-exist test the broad notion lacks — a specialization of essentialism narrowed to persistence-over-time. Not every essential property is identity-providing.

Path to root: Identity-Providing Kind → Criteria of Individuation

Neighborhood in Abstraction Space

Identity-Providing Kind sits among the more crowded primes in the catalog (21st percentile for distinctiveness): several abstractions describe nearly the same structure, so a description that fits it will tend to fit its neighbors too — transporting it usually means disambiguating within this family rather than landing on it exactly.

Family — Identity, Reference & Placeholders (10 primes)

Nearest neighbors

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

Not to Be Confused With

The embedding-nearest neighbor, institution (similarity 0.84), is a confusion that arises mostly because the prime's clearest applied cases are institutional — corporate personhood, legal continuity. An institution is a durable, rule-governed social structure that, among other things, confers identity-providing status: it is the legal regime that declares a corporation a continuing person across changes of officers, or that makes a natural person identity-providing across every role they occupy. But the identity-providing kind is not the rule-system; it is the category that bears persistence criteria for an instance. The institution may be the source of that criterion in stipulated cases, yet the prime applies equally where no institution is involved — human being is identity-providing for a person, organism for a living thing, by nature and not by decree. Tension T4 names exactly this split: for natural kinds the identity-provision is discovered, for legal and software entities it is stipulated by a rule-system. A practitioner who fuses the two will assume identity-provision always requires an institution to confer it (and so miss the natural cases), or treat the institution itself as the thing that persists rather than as what assigns persistence to something else.

A second confusion is with role — and this is the prime's defining contrast rather than a peripheral one, because the entire cease-to-exist test exists to separate them. A role is a position an instance occupies temporarily: employee, defendant, office-holder, logged-in user. It fails the cease-to-exist test — the instance survives losing the role — and so, by the single-bearer invariant, it cannot be the identity-providing kind. The identity-providing kind is precisely the one category whose loss would end the instance. The two are constantly conflated because the salient way we describe someone is usually by their current role, and the strong pull (tension T1) is to type an entity by what it is doing now. The cost of the confusion is the prime's canonical bug: model the role as the kind, and the instance vanishes when the role ends — deactivating an account loses the person, graduation annihilates the student. The discipline is to demote every role to a predicate the persisting instance gains and loses, and reserve identity-provision for the underlying kind.

A third confusion, sharper in formal settings, is with classification and the broader ontology it lives in. Classification assigns an instance to the categories it satisfies; it produces the set of an instance's memberships. The identity-providing kind asks a question classification never reaches: among those satisfied categories, which one supplies the instance's persistence criteria? Classification can correctly record that a person is a human, a student, an employee, and a taxpayer all at once, yet say nothing about which of these the person cannot survive losing. Likewise an ontology is the whole specification of categories and relations, while the identity-providing kind is one meta-property within it (the rigidity / +I distinction operationalized by frameworks like OntoClean). Confusing the prime with classification or ontology-in-general leads a modeler to think a complete category assignment has settled identity, when the load-bearing persistence question is still untouched — which is exactly how the role-as-type bug slips into well-classified systems.

These distinctions matter because each protects a different commitment. Holding the identity-providing kind apart from institution keeps both the natural (discovered) and the stipulated (conferred) cases in view, rather than assuming identity always needs a rule-system. Holding it apart from role preserves the single-bearer invariant and the cease-to-exist test that block the vanishing-instance bug. And holding it apart from classification and ontology keeps the persistence question — which satisfied category supplies identity over time — as the explicit, separate move it must be, rather than something a complete category assignment is mistakenly assumed to have already answered.

Solution Archetypes

No catalogued solution archetypes reference this prime yet.