EM-XCT-01 · Shared contract · W0
Identity and external ID matching
A shared contract for identifiers, aliases, same-as claims, merge/split and reversible mappings.
Partially published; research continues
Claude: independent-study-and-three-audit-rounds-complete-final-accept-with-limits; Grok: independent-study-and-three-audit-rounds-complete-final-accept-with-limits.
Published results
Research note, in Russian: Account ownership and delegation; full assignment-observation history; policy rotation/federation and disclosure; merge/split and erasure; inverse subject index; production transactional adapters and scale testing; broad parent source/field/relationship ratification. 0.1.0 is a bounded companion-validated reference, not complete enterprise identity.
Subject boundary and candidate types
- IdentifierBinding
- IdentityAssertion
- IdentityResolution
Deep research questions
- What evidence permits a merge?
- How to distinguish a collision from an alias?
- How to undo an erroneous merge?
Verifiable invariants
- An ID is qualified by scheme and issuer
- An email match is not sufficient
- A merge has a history and a reversal plan
End-to-end acceptance scenario
Three IDs are linked to one person, a collision remains contested, and an erroneous merge can be corrected.
Negative case
HR, tracker and git create three Persons, or get merged by name.
Approaches to compare
- Current Vercy protocol/MMAS/whole-object and the published WM-XCT
- W3C PROV/SKOS/SHACL/ODRL where applicable
- Practice of source connectors, versioned schemas and policy enforcement
Candidates in the live catalogue
- WM-XCT-011 · Identifier Scheme · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-XCT-036 · Alias / Same-as Mapping · 0.3.2-enterprise.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.