Abstract Work Register¶
A canonical register — instantiates Carrier-Independent Work Identity Governance
The canonical, resolver-backed record that fixes what a work's identity is and who may speak for it, so every carrier points back to one authoritative source.
When an identity is used across many carriers — employers, platforms, formats, repositories — the first failure is that each carrier quietly mints its own version and they drift apart. Abstract Work Register is the single authoritative record that stops that drift: it states what the identity is, binds it to a persistent identifier, names who has authority to amend it, and scopes the rights and obligations that travel with it. Its defining move is resolution — it is not a description of the work but the one place every copy, profile, or edition is supposed to resolve back to when the question is "which of these is the real one, and who says so." It asserts identity and authority; it deliberately leaves the evidence, the inventory, and the sameness test to other mechanisms.
Example¶
A registered nurse practices across three hospital systems, a travel-nursing platform, and a state licensure board over her career. Each of those carriers holds a profile of her — credentials, employment record, reputation — and left alone they diverge: one lists a lapsed certification, another a maiden name, a third a stale specialty. The Abstract Work Register is the carrier-independent record that binds them: a persistent identifier (a real-world example is the National Provider Identifier, or an ORCID iD for a researcher's scholarly identity), a statement of who this professional identity is, a note of who may change the record (she and the licensure authority, not any single employer), and the scope of what the identity entitles and obliges across settings. Each hospital's HR system and the platform profile are then supposed to resolve to this record rather than assert a competing truth — so when they disagree, there is an authoritative source to settle it.
How it works¶
The register does one thing the other mechanisms cannot: it is the authoritative point of resolution. Concretely it (1) assigns a persistent identifier meant to outlive any carrier; (2) records the identity statement — the minimal declaration of what this work/identity is; (3) records the authority and resolver — who may amend the record and how carriers locate the canonical version; and (4) records the rights-and-obligations scope. It indexes pointers to manifestations, provenance, and fork decisions produced elsewhere, but it does not generate them — it is the hub they resolve to, not the machinery that fills them in.
Tuning parameters¶
- Authority model — single custodian, delegated, or self-sovereign. Tightens control at the cost of portability, or maximizes portability at the cost of a clear amender.
- Identifier scheme — opaque-and-permanent versus human-readable. Permanence survives rebrands; readability aids humans but tempts reuse.
- Resolution binding — how strongly carriers are required to resolve back (advisory pointer versus enforced). Stronger binding kills drift but demands cooperation from every carrier.
- Scope granularity — how finely the rights/obligations note is drawn. Fine scope prevents authority-borrowing; coarse scope is cheaper to maintain.
- Openness — public register versus closed. Openness aids trust and third-party resolution; closure protects sensitive identity data.
When it helps, and when it misleads¶
Its strength is that it gives a scattered identity one address: a place to answer "which is authoritative, and who may change it." That is the load-bearing input every other mechanism in the archetype leans on.
Its failure mode is that a register asserts continuity — it does not prove it. A single authoritative record is exactly the thing worth capturing, and worth capturing wrongly: it can go stale, become a bottleneck, or suffer authority capture, where whoever controls the record controls "the truth" regardless of the underlying reality. The classic misuse is to edit the record to launder a replacement as continuity — quietly swap the work behind a trusted identifier so the new thing inherits the old one's citations, rights, and trust. The discipline that guards against this is to keep the assertion (this register) separate from the evidence (Archival Provenance Metadata Template) and the criterion (Identity Preservation Checklist), and to require provenance to back any change of substance — the register's own tradition of authority control is precisely this: one authoritative record, but one that must be earned, not merely declared.[n1]
How it implements the components¶
Abstract Work Register realizes the identity-and-authority core of the archetype — the components that establish who and what, not how much may vary or what actually exists:
work_identity_statement— it holds the explicit declaration of what the work's identity is.authority_and_resolver_record— it records the persistent identifier, who may speak for the work, and how carriers resolve to the canonical version.rights_and_obligations_scope_note— it scopes which rights and obligations travel with the identity across carriers.
It does not test whether a given instance still qualifies as the work (Identity Preservation Checklist and Identity Boundary-Case Table), enumerate the concrete manifestations (Edition and Manifestation Catalog), or evidence the history (Archival Provenance Metadata Template).
Related¶
- Instantiates: Carrier-Independent Work Identity Governance — the register is the authoritative hub the whole appraisal resolves to.
- Sibling mechanisms: Edition and Manifestation Catalog · Persistent-Identifier Resolution Policy · Archival Provenance Metadata Template · Fork Decision Record · Governed Translation or Adaptation Review · Identity Boundary-Case Table · Identity Preservation Checklist · Migration Context Preservation Plan · Semantic Diff Review · Version Lineage Graph · Work–Expression–Manifestation Matrix
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: The mechanism is the canonical, resolver-backed record that fixes what a work's identity is and who may speak for it, so every carrier points back to one authoritative source, so its operative form is an accumulating history or provenance record.
Independent corroboration: The frozen evidence defines Abstract Work Register as 'The canonical, resolver-backed record that fixes what a work's identity is and who may speak for it, so every carrier points back to one authoritative source', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Library & Information Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Authority control, canonical records, persistent identifiers, manifestations, and resolver-backed identity are core library, archival, and information-science practices.
Related originating lineages:
- Computer Science & Software Engineering — Identifier resolution and distributed reference infrastructure supply the technical implementation.
- Law & Governance — Rights, obligations, amendment authority, and legal identity continuity materially shape the governance layer.
Review resolution: Library authority control and work identity are primary, but the page generalizes them through resolver infrastructure and legal authority, so cross-disciplinary Encyclopedia synthesis is accurate.
Attribution caveat: The page generalizes bibliographic authority control from works to professional and institutional identities.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The register asserts identity; it does not constitute it. A work can be the same work with no register, and a register can be dead wrong. Its authority is only as good as the provenance and criterion behind it — which is why keeping those in separate mechanisms, rather than folding them into the record, is what keeps the record honest.
[n1] In library and information science, authority control is the practice of maintaining a single authoritative, uniquely identified record for an entity — a person, work, or subject — so that every variant reference resolves to the same controlled record rather than proliferating into unlinked duplicates. It is the register's job done well; its failure is when the controlled record is trusted past the point it is true. ↩