← Back to catalogue
Previous version

Identity Register

vr.wm-per-002 · world-r4-identity-register

Anchoring identity of persons, orgs, things

World Models Society, people and institutions SOC.PER.DIG

Bundle → Layer → Finding → Questions Incomplete

4 bundles · 8 layers · 0 findings · 0 questions

anchor The identity record itself

subjectKind

person, organization and thing subjects and what an anchor asserts for each

identityLifecycle

registered, active, suspended, retired states and same-subject continuity

binding What attaches to an anchor

identifierSchemes

bindings of scheme-governed identifiers to the anchor

keyAndCredentialBinding

cryptographic keys and authenticators bound for proof of control

assurance How strongly identity is established

proofingEvidence

the evidence trail from identity proofing

assuranceLevel

graded confidence attached to the anchor and its bindings

resolution Answering lookups without oversharing

resolutionService

identifier to status-and-keys resolution

privacyControls

minimal-disclosure rules, verification without attribute release

Note: Legacy card: layers named, findings and questions never written.

Classifiers Filled

Family
World Models
Category
Society, people and institutions
Entry kind
standalone-mm
Navigation path
NAV.SOC.PER.DIG
Domain
SOC.PER.DIG
Industry
Cross-industry
Tags
digitalidentityaccountsoc.per.dig
Also called
R4

What it is Derived, awaiting review

The anchoring of identity for persons, organizations and things: one authoritative record per subject, to which identifiers, keys and assurance evidence are bound, and against which the rest of the world resolves "who or what is this".

Note: First sentence of the legacy card introduction.

Why it exists Filled

Anchoring identity of persons, orgs, things

Distinguishing features Derived, awaiting review

  • It is its own meta-model because identity anchoring, identifier binding and assurance are a distinct discipline from any profile data about the subject: the register says that a subject exists and is the same one over time, and deliberately says as little else as possible.

What robots and AI may and may not do Missing, in the backlog

Not described yet. This gap is in the card backlog.

Moral aspects Derived, awaiting review

  • Any resolution or disclosure beyond the public resolver view is granted through the S1/S2 access and consent models and audited via S4.

Owners Filled

Steward

The identity registrar owns the anchors and their bindings and answers for uniqueness and continuity, while each subject holds inspection rights over their own record.

Links to other meta-models Filled

extends

  • world.registry - the identity register is a specialization of the register pattern, with anchoring as its legal effect

references

  • world.person - a person anchor points to, and never inlines, the person's profile kept elsewhere
  • world.organization - organization anchors resolve to organization records governed in their own model
  • world.attestationCertificateAndLicense - issuers and subjects of attestations are anchored here
  • world.lifeEventsAndCivilStatus - birth registration creates a person anchor, death registration retires it

composes

  • world.audit - every resolution and update carries the audit facet

imports

  • w3c-did - ALIGN: decentralized identifier syntax, resolution and key rotation semantics
  • iso-iec-24760 - ALIGN: identity management vocabulary and lifecycle framing
  • nist-sp-800-63 - ALIGN: identity proofing and assurance level semantics

What else AI and robots need to interact with it Incomplete

Identity and identifiers required Derived, awaiting review

  • identifierBinding: an externally schemed identifier attached to an anchor; key attributes: scheme, value, boundAt, status

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: no invented physical properties.

Recognition optional Missing, in the backlog

Not described yet. This gap is in the card backlog.

Capabilities and actions required Derived, awaiting review

  • identityRegistered: a new anchor was created for a proofed subject
  • identifierBound: an external identifier was attached to an anchor
  • identifierRetired: an identifier binding was ended without ending the anchor
  • keyRotated: a control key was replaced and the old one retired
  • assuranceRaised: re-proofing lifted the anchor's assurance level
  • identitySuspended: the anchor was temporarily barred from resolution and use
  • identityRetired: the anchor was closed, typically on death or dissolution, with continuity preserved for history
  • recordsLinked: two anchors were asserted to denote the same subject

Legacy events listed as state transitions.

Hazards and failure modes optional Missing, in the backlog

Not described yet. This gap is in the card backlog.

Standards and interfaces required Derived, awaiting review

  • resolutionContract: which attributes a class of relying parties may obtain when resolving an identifier
  • verificationContract: yes/no confirmation of a claimed binding or status without releasing attributes
  • registrarUpdateContract: who may create, bind, suspend and retire anchors, under which evidence rules
  • subjectAccessContract: the subject's standing right to see their own full record and its access history
  • publicResolverView: identifier to current status and public keys; omits personal attributes and evidence
  • relyingPartyView: status plus assurance level for an authorized verifier; omits proofing evidence content
  • subjectSelfView: the complete own record including bindings, assessments and access history

Context of use required Filled

  • Any resolution or disclosure beyond the public resolver view is granted through the S1/S2 access and consent models and audited via S4.

Sources Missing, in the backlog

Not described yet. This gap is in the card backlog.

Open questions

  • Superseded by a researched world model? Map this legacy card to its successor or retire it.

Machine files

Provenance

legacy MMAS card (world-models v0.2) · legacy

Built from: models/world-r4-identity-register/spec.yaml, models/docs/registries-ledgers/R4-identity-register.md