Identity Test¶
Core Idea¶
An identity test is the rule that decides, in a given system, when two presentations refer to the same entity. "Same entity" is not a primitive fact but a function of the kind in question, the criterion sufficient to fix sameness, and the operations a positive answer licenses — so the test partly constitutes the count it produces.
How would you explain it like I'm…
Same Dog or Two?
Imagine two photos. Are they the SAME dog photographed twice, or two dogs that just look alike? You need a rule to decide — maybe 'same dog if it has the same little white ear.' An identity test is the rule you use to decide whether two things you're looking at are really one and the same thing.
One Thing or Two?
Lots of times you have to decide: is this one thing I'm seeing twice, or two different things that happen to resemble each other? An identity test is the rule that settles that. It depends on what kind of thing it is, which features count as 'enough to be the same,' and what you'll DO once you decide — like merging two records into one, or counting something once instead of twice. The big surprise is that different tests give different answers from the very same data: pick one rule and you count three things, pick another and you count five. There's no secret 'true' count hiding underneath — the test you choose is part of what decides the answer.
The Rule for Sameness
An identity test is the rule that decides, in a given system, when two presentations refer to the same entity. The structural point is that 'same entity' isn't a primitive fact about reality but a function of three things: what kind of entity is in question, which property or properties suffice to fix sameness for that kind, and what operations a positive answer licenses — merge the records, hold the same party accountable, count once not twice. Different identity tests produce different counts, histories, and allocations of credit or blame from identical underlying data. The pattern recurs because almost any system that records a domain must draw the line between one thing seen twice and two things that merely resemble each other, and the choice of test fixes that line — 'same person' under legal rules is a different predicate than 'same person' under psychological-continuity philosophy. There is no test-independent count waiting to be discovered; the test partly constitutes the entity being counted. The prime forces four moves: name the kind, name the test, name the equivalence regime (is it reflexive, symmetric, transitive — genuine equivalence classes, or something weaker?), and name the downstream operations relying on its verdicts.
An identity test is the rule that decides, in a given system, when two presentations refer to the same entity. The structural commitment is that 'same entity' is not a primitive fact about reality but a function of three things: what kind of entity is under discussion, what property or set of properties is sufficient to fix sameness for that kind, and what operations are licensed by a positive answer — merge records, hold the same party accountable, treat two reports as the same event, count once rather than twice. Different identity tests produce different counts, different histories, and different allocations of credit, blame, or cost from the same underlying data. The pattern recurs because almost every system that records or reasons about a domain must draw the line between one thing seen twice and two things that resemble each other, and the choice of test fixes the answer: a biological kind individuated by one criterion yields different boundaries than the same kind by another; 'same person' under legal-identity rules is not the predicate 'same person' under psychological-continuity philosophy; 'same software release' under version-number rules differs from 'same release' under binary-equivalence rules. There is no test-independent count waiting to be discovered — the test partly constitutes the entity being counted. The prime forces four moves: name the kind whose identity is at stake; name the test, the operational criterion resolving any candidate pair as same or distinct; name the equivalence regime — is the test reflexive, symmetric, transitive, yielding genuine equivalence classes, or some weaker structure?; and name the downstream operations that rely on its verdicts. Many disputes about classification, accountability, deduplication, and counting dissolve once these four are explicit, and many durable disputes survive precisely because the parties hold implicitly different identity tests over the same data.
Broad Use¶
- Databases: record linkage and entity resolution — probabilistic matching, deterministic keys, deduplication.
- Ontology engineering: classes tagged with whether they carry an identity criterion, so hierarchies do not smuggle in incompatible ones.
- Law and forensics: layered tests — registration, biometric, witness, genetic — each with its own error profile.
- Biology: competing species concepts and molecular tests for "same individual" or "same protein."
- Historiography: whether a battle named in one chronicle is the same as one named in another.
- Software: the menagerie of equalities — reference, structural, value, semantic, content-hash.
Clarity¶
Shows that disputes apparently about facts — are these two the same? — are often disputes about which test is in force over the same data.
Manages Complexity¶
Compresses unbounded pairwise sameness judgments into a single maintained rule applied at scale, with a tunable false-merge / false-split operating point.
Abstract Reasoning¶
Lets any test be studied as an artifact — its error rates, its monotonicity, its drift under data evolution — independent of any particular case.
Knowledge Transfer¶
- Epidemiology: census record-linkage methods build longitudinal cohorts from administrative data with no common key.
- Version control: cryptographic content-hash identity ports into content-addressed storage and supply-chain attestation.
- Genomics: phylogenetic identity-by-monophyly reused as pandemic lineage and clade definitions.
Example¶
A health system building a longitudinal patient record discovers the whole problem is the matching test: too loose and one patient's allergy lands on another's chart; too strict and a contraindication is fragmented across phantom identities.
Relationships to Other Primes¶
Parents (1) — more general patterns this builds on
- Identity Test is a kind of Criteria of Individuation — child of emergent criteria_of_individuation
Path to root: Identity Test → Criteria of Individuation
Not to Be Confused With¶
- Identity Test is not a Relation because a relation is any structured tie between entities, whereas an identity test is the specific operational criterion that resolves co-reference for a kind, with its equivalence regime and downstream operations.
- Identity Test is not an Equivalence Relation because an equivalence relation is the abstract algebraic structure (reflexive, symmetric, transitive), whereas an identity test is a designed, fallible criterion that may break those axioms (NaN, non-transitive comparators).
- Identity Test is not Classification because classification sorts entities into kinds (what type is this?), whereas an identity test resolves co-reference within a kind (are these two the same individual?) after the kind is fixed.