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.
Bundle → Layer → Finding → Questions Filled
2 bundles · 3 layers · 4 findings · 10 questions
Person identity The minimal identity of a natural person, kept apart from roles.
Identity and evidence
Who the person is and what proves it.
Identity evidence
The proof behind binding a record to a person.
- Which evidence supports binding this record to this person?
- Is a pseudonym or local identifier enough for the purpose at hand?
- Are two records with the same display name the same person, and on what proof?
Name forms
Names over time and across scripts.
- Which name forms has the person used, and for which periods?
- Does a name change keep the history without disclosing it to every consumer?
Contacts and disclosure Permitted contact points and purpose-bound disclosure.
Contact points
Contacts with purpose and validity.
Contact purpose
Each contact point with the purpose it may be used for.
- For which purposes may this contact point be used?
- Is an email address being used as an identity key rather than as a contact?
Bindings
How HR, customer and technical roles refer to the person.
Role binding
Roles referring to the person under a disclosure agreement.
- Which systems reference this person, and under which disclosure terms?
- Is an uncertain match between systems still held as a suggestion?
- Does any employer or system claim ownership of all data about the person?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterprisePEO
- Industry
- Cross-industry
- Tags
- EM-PEO-01W1subjectPersonNameFormContactPointIdentityEvidence
What it is Filled
The minimal identity of a natural person and permitted contacts. HR, customer and technical roles reference the person under a disclosure agreement.
Why it exists Filled
The minimal identity of a natural person and permitted contacts. HR, customer and technical roles reference the person under a disclosure agreement.
Distinguishing features Filled
- Identity binds records to a person only on evidence, never on name similarity alone.
- Personal data is disclosed to each consumer only for its stated purpose.
- The person exists apart from employment, customer and account roles.
- Distinct from the employee profile, which belongs to one work relationship.
What robots and AI may and may not do Filled
Must not
- Merge two users automatically because they share a display name.
- Use an email address as proof that two records are one person.
- Disclose a former name to consumers that do not need it.
- Treat an employer as the owner of all data about a person.
- Promote an uncertain match to a confirmed identity without review.
Only with a human decision
- Confirming a merge of two person records.
- Disclosing personal data beyond the agreed purpose.
- Correcting identity evidence after a dispute by the person.
May
- Suggest possible matches between records with the evidence for each.
- Return only the attributes a consumer's purpose allows.
- Record name changes as new name forms with periods.
Moral aspects Filled
- False merges mix up people's records and can expose one person's data to another.
- Over-disclosure of names and contacts invades privacy and can endanger people who changed names.
- People have rights to access and correct data held about them.
Who is affected
- The person concerned
- Namesakes
- Employers and service providers holding records
Owners Filled
Steward
The head of HR or the person accountable for workforce records.
Master systems
- HRIS
- Identity and access management system
- Customer relationship management system
Links to other meta-models Filled
neighbor
- EM-COM-01
- EM-LEG-01
- EM-ORG-03
- EM-ORG-05
- EM-PEO-02
- EM-PEO-03
references
- WM-PER-001 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by a person identifier issued by the holding system, bound to other systems only through evidence-based links.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- A record holds name forms, contact points and identity evidence, without role data.
- Often confused with user accounts, employee profiles or customer contacts.
Capabilities and actions required Filled
- Link one person across systems while keeping uncertain matches as suggestions.
- Serve purpose-limited views of the same person to different consumers.
Hazards and failure modes required Filled
- Merging namesakes into one person.
- Leaking former names or private contacts through broad views.
Standards and interfaces required Filled
- IETF RFC 6350 vCard format for contact data.
- W3C Verifiable Credentials Data Model for identity evidence.
- ISO/IEC 29100 privacy framework.
Context of use required Filled
- Used wherever HR, customer and access systems need to refer to the same person.
- Data protection law such as the GDPR governs processing of this record.
Sources Filled
- 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
- Principles and Recommendations for a Vital Statistics System, Revision 3 (Series M No. 19/Rev.3) - Carried over from the published world model wm-per-001-person; checked live (HTTP 200) on 2026-10-09.
- United Nations Strategy for Legal Identity for All (UN Legal Identity Agenda) - Carried over from the published world model wm-per-001-person; checked live (HTTP 200) on 2026-10-09.
- ISO/IEC 24760-1:2025 Information security, cybersecurity and privacy protection - A framework for identity management - Part 1: Core concepts and terminology - Carried over from the published world model wm-per-001-person; checked live (HTTP 200) on 2026-10-09.
Open 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?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-peo-01/brief.json, ver-cy/world-models/card-supplements/em-peo-01.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.