Identity Boundary-Case Table¶
A calibration test table — instantiates Carrier-Independent Work Identity Governance
A curated set of clearly-same, clearly-new, and contested instances used to pressure-test and calibrate the work-identity criterion.
A sameness criterion sounds fine in the abstract and fails at the edges. Identity Boundary-Case Table is the calibration instrument that finds those edges before a real dispute does: a curated corpus of instances labelled clearly the same work, clearly a new work, and contested, run against the current identity criterion to see where it agrees with judgment and where it breaks. Its defining function is empirical calibration — it does not state the rule or decide a live case; it is the standing regression suite for the rule, and the clearly-same rows collectively map out the zone of variation the work is allowed to undergo while staying itself.
Example¶
Take a song. Is a live acoustic performance the same work as the studio single? A remaster? A radical remix? A karaoke instrumental with the vocal stripped? A new track built on a two-second sample? The Identity Boundary-Case Table collects these as labelled rows — same, new, contested — and runs the current criterion over them. It surfaces where the criterion misfires: perhaps the rule wrongly calls the sample-based track "the same work," or wrongly splits the remaster into a new one. And by gathering everything labelled same — the live version, the remaster, the acoustic take — it delineates the allowed variation zone: tempo, key, arrangement, and production may vary; the melody and lyric core may not. That zone, discovered by example, is what a criterion or a fork threshold can then be tuned against.
How it works¶
What distinguishes it from a live ruling is that it is a labelled corpus, not a case: a spread of instances chosen to straddle the boundary, each with a ground-truth label, used to test the criterion in bulk. The contested rows carry the most value — they are where the criterion earns or loses trust. Running the criterion over the table yields a pass/mislabel pattern; the clearly-same rows aggregate into the allowed-variation zone. It calibrates the rule; it does not author the rule, and it does not adjudicate any single new instance.
Tuning parameters¶
- Case coverage — how many and how varied the instances are, especially near the boundary. Dense boundary coverage calibrates finely; sparse coverage leaves blind spots.
- Labelling authority — who assigns the ground-truth label, and whether by one judge or a panel. Panel labels are more defensible; single-judge labels are faster but partial.
- Contested-case weight — how much attention the ambiguous rows get. Leaning into them stresses the criterion hardest; ignoring them flatters it.
- Refresh cadence — how often the table is re-run and extended. Frequent refresh keeps it live; neglect lets it rot into a museum of settled cases.
- Revision trigger — how many mislabels prompt reworking the criterion. A tight trigger keeps the rule sharp; a loose one tolerates known gaps.
When it helps, and when it misleads¶
Its strength is that it turns a vague, arguable criterion into something testable: it exposes where the rule breaks on paper, cheaply, before the break costs a real dispute — and it makes the allowed-variation zone concrete rather than asserted.
Its failure modes are staleness and stacking the deck. A table that stops being re-run becomes a museum of settled cases and silently drifts out of date as the domain and the criterion change. Cases can be cherry-picked to flatter a criterion someone has already chosen, and a criterion can be overfit to the table until it passes the examples but generalizes poorly — the identity analogue of teaching to the test. Its classic misuse is assembling cases to justify a rule already decided rather than to challenge it. The discipline that guards against this is to keep adding fresh and adversarial cases — including ones that would embarrass the current rule — and to re-run the table whenever the criterion changes. The puzzle it exists to make tractable is the old Ship of Theseus: identity under incremental replacement, boundary and all.[n1]
How it implements the components¶
Identity Boundary-Case Table realizes the calibration side of the archetype — the components that test the rule rather than state or apply it:
instance_equivalence_test_set— it is the curated, labelled set of instances used to test whether two instances count as the same work.allowed_variation_zone— by aggregating the clearly-same cases, it empirically delineates which variations are tolerated without breaking identity.
It does not state the criterion it tests (Identity Preservation Checklist and the Work Identity Statement in the Abstract Work Register), fix the fork threshold for a live change (Fork Decision Record), or set the semantic change budget (Semantic Diff Review).
Related¶
- Instantiates: Carrier-Independent Work Identity Governance — it is the test bed that keeps the identity criterion trustworthy.
- Consumes: Identity Preservation Checklist supplies the criterion the table pressure-tests; Abstract Work Register supplies the identity statement the cases are judged against.
- Sibling mechanisms: Identity Preservation Checklist · Fork Decision Record · Abstract Work Register · Archival Provenance Metadata Template · Edition and Manifestation Catalog · Governed Translation or Adaptation Review · Migration Context Preservation Plan · Persistent-Identifier Resolution Policy · Semantic Diff Review · Version Lineage Graph · Work–Expression–Manifestation Matrix
Editorial Notes¶
Form Classification¶
Form family: Experiment, Test & Rehearsal
Rationale: Curated clearly-same, clearly-new, and contested instances are deliberately run against the identity criterion to expose and calibrate its boundary behavior.
Nearest alternative: Representation, Specification & Plan — The cases form a durable table, but their operative use is active pressure-testing rather than passive reference.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Philosophy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Calibrating sameness through clearly same, clearly new, and contested cases is applied philosophical work on identity persistence.
Related originating lineages:
- Law & Governance — Authorship, work identity, and contested versions also have material intellectual-property consequences.
- Library & Information Science — Work and edition identity materially supply carrier-independent boundary cases.
- Material Culture & Museum Studies — Conservation and object biography independently confront when restoration or replacement creates a new object.
Review resolution: Both reviewers independently assign philosophy as the primary originating domain, so that shared primary is retained. Alternate domains are the union of reviewer-identified formative or independently originating lineages; later application settings alone are excluded. The final form materially composes methods or concepts from more than one formative domain. It has established independent use across several domains, but that does not make it domain-free. The encyclopedia entry makes that composition explicit.
Attribution caveat: The table operationalizes the Ship-of-Theseus problem for governed work identity.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
The table validates; it does not decide. A contested row is a signal — to sharpen the criterion, or to escalate the case through the dispute path — never a ruling in itself. And its value decays if it is not re-run: a boundary-case table that is written once and shelved calibrates the criterion as it was, not as it is.
[n1] The Ship of Theseus is the classical puzzle of whether an object whose parts are replaced one by one remains the same object — and if not, at which replacement it stopped. It is the canonical statement of the problem this table exists to make tractable: identity persistence under incremental change. ↩