EM-PEO-01 · Subject model · W1
Person and Contextual Identity
The minimal identity of a natural person and permitted contacts. HR, customer and technical roles reference the person under a disclosure agreement.
Partially published; research continues
Claude: complete-frozen-study-and-single-audit-remediated; Grok: complete-reconciled.
Published results
Research note, in Russian: Canonical/runtime promotion remains governed by the package allocation, identity and dependency holds.
Subject boundary and candidate types
- Person
- NameForm
- ContactPoint
- IdentityEvidence
Deep research questions
- How are namesakes distinguished, and how is merging people by email avoided?
- When is a pseudonym or a local identifier sufficient?
- How is a name change supported without losing history or over-disclosing?
Verifiable invariants
- Identity requires proof
- Personal data is disclosed by purpose
- An employer does not become the owner of all data about a person
End-to-end acceptance scenario
Three systems, two namesakes and a name change yield correct bindings; an uncertain match remains a suggestion.
Negative case
Two users with the same display name are merged automatically.
Approaches to compare
- HR Open: exchange of HR data
- W3C ORG and ESCO/SFIA: relationships, skills and levels of responsibility
- HRIS/ATS/LMS practice and independent verification of outcome measurement via SPACE
Candidates in the live catalogue
- WM-PER-001 · Person · 0.3.0-research.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.