{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-xct-016","code":"wm-xct-016-identity-register","url":"https://ver.cy/models/wm-xct-016-identity-register/","name":"Identity Register","alternateNames":["R4"],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Cross-cutting context","entryKind":"registry","plane":"","domain":["XCT.IDREG"],"industry":["Cross-industry"],"navPath":"NAV.XCT.IDREG","tags":["identity","register","xct.idreg"],"facets":{}},"whatItIs":"Owns register and namespace identity, entry anchors, identifier and alias bindings, registration and assignment evidence, assurance, lifecycle, entity-resolution assertions, merge and split lineage, purpose-bound resolution, federation mappings, subject rights, access and retention. Subject profiles, credentials, accounts, authentication factors, keys, authorization decisions, source documents and business lifecycle remain external.","purpose":"Provide a governed, durable and source-qualified registry pattern for anchoring and resolving identifiers of persons, organizations, devices, services and things without importing their descriptive master data.","scope":{"in":["Register authority and profile, namespace, identifier scheme, syntax, canonicalization, comparison, uniqueness, persistence, non-reuse and resolver contract","Entry identity and external subject reference, identifier bindings, minimal aliases, assignment and proofing evidence, assurance, quality, conflicts, lifecycle and entity resolution","Federation and loss-aware mappings, purpose-bound projections, privacy, subject rights, access, retention, disposition and safe agent operations"],"out":["Person, organization, device, service, thing, credential, account, authentication factor, key, authorization policy, source document or audit-log master lifecycle","Biometric algorithms, credential issuance, authentication execution, access decisions, universal name authority or copying full subject profiles into the register","Guarantees of universal identity truth, cross-register equivalence, legal identity, eligibility or rights that are not established by a named authority and jurisdiction"],"boundaries":[{"neighbor":"Person, Organization, Device, Service or Thing","distinction":"The register stores a minimal external subject reference and identity assertions; each subject model owns descriptive, physical, functional and contextual properties."},{"neighbor":"Credential / Attestation","distinction":"A credential owns issuer claims and validity; the register may cite it as evidence without becoming its issuer, holder or status list."},{"neighbor":"Account / Authentication / Key","distinction":"An entry or identifier can be linked to an account, authenticator or controlled identifier, but lookup does not prove possession or authorize access."},{"neighbor":"Entity Resolution / Master Data","distinction":"This pattern records identity-specific candidate matches, equivalence and lineage; descriptive golden-record consolidation remains in domain master-data models."},{"neighbor":"Authorization / Decision / Audit Log","distinction":"Resolution and assurance are evidence for external decisions, while the model keeps identity-specific provenance and delegates generic logging and authorization."}]},"distinguishingFeatures":["Anchors identifiers for subjects without owning their profile, account, credential or keys.","Records match and equivalence as assertions with evidence, not as automatic merges.","Keeps merge, split and supersession lineage so old identifiers still resolve.","Resolves identifiers purpose-bound rather than as open lookups."],"structure":{"bundles":[{"id":"register-authority-namespace-and-scheme","name":"Register authority, namespace and scheme","description":"Defines the identity register itself and the governed identifier space it operates.","layers":[{"id":"register-identity-mandate-and-profile","name":"Register identity, mandate and profile","description":"Establishes who operates the register, under what mandate and for which subject domain.","findings":[{"id":"register-identifier-owner-steward-mandate-and-jurisdiction","name":"Register identifier, owner, steward, mandate and jurisdiction","description":"Stable register identity, accountable operator, registrar, steward, legal or policy mandate, jurisdiction and authoritative service references.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define register identifier, owner, steward, mandate and jurisdiction?","id":"register-identifier-owner-steward-mandate-and-jurisdiction-q01","kind":"identity"},{"text":"Which source, evidence, event time, effective time and knowledge time support register identifier, owner, steward, mandate and jurisdiction?","id":"register-identifier-owner-steward-mandate-and-jurisdiction-q02","kind":"evidence"},{"text":"How may register identifier, owner, steward, mandate and jurisdiction be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"register-identifier-owner-steward-mandate-and-jurisdiction-q03","kind":"validation"}]},{"id":"register-profile-subject-domain-authoritative-scope-and-version","name":"Register profile, subject domain, authoritative scope and version","description":"Profile identity and version, supported subject kinds, authoritative assertions, exclusions, predecessor and compatibility status.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define register profile, subject domain, authoritative scope and version?","id":"register-profile-subject-domain-authoritative-scope-and-version-q01","kind":"definition"},{"text":"Which source, evidence, event time, effective time and knowledge time support register profile, subject domain, authoritative scope and version?","id":"register-profile-subject-domain-authoritative-scope-and-version-q02","kind":"authority"},{"text":"How may register profile, subject domain, authoritative scope and version be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"register-profile-subject-domain-authoritative-scope-and-version-q03","kind":"interoperability"}]}]},{"id":"namespace-scheme-and-identifier-rules","name":"Namespace, scheme and identifier rules","description":"Makes identifier meaning, comparison and persistence explicit.","findings":[{"id":"namespace-scheme-authority-syntax-canonical-form-and-comparison","name":"Namespace, scheme authority, syntax, canonical form and comparison","description":"Namespace and scheme identifiers, naming authority, grammar, character and case rules, canonical form, parser, validator and equality rules.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define namespace, scheme authority, syntax, canonical form and comparison?","id":"namespace-scheme-authority-syntax-canonical-form-and-comparison-q01","kind":"relationship"},{"text":"Which source, evidence, event time, effective time and knowledge time support namespace, scheme authority, syntax, canonical form and comparison?","id":"namespace-scheme-authority-syntax-canonical-form-and-comparison-q02","kind":"temporal"},{"text":"How may namespace, scheme authority, syntax, canonical form and comparison be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"namespace-scheme-authority-syntax-canonical-form-and-comparison-q03","kind":"access"}]},{"id":"uniqueness-scope-persistence-reassignment-reservation-and-resolution-policy","name":"Uniqueness scope, persistence, reassignment, reservation and resolution policy","description":"Uniqueness domain, minting strategy, collision handling, persistence, non-reuse or reassignment rule, reserved ranges and resolver contract.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define uniqueness scope, persistence, reassignment, reservation and resolution policy?","id":"uniqueness-scope-persistence-reassignment-reservation-and-resolution-policy-q01","kind":"requirement"},{"text":"Which source, evidence, event time, effective time and knowledge time support uniqueness scope, persistence, reassignment, reservation and resolution policy?","id":"uniqueness-scope-persistence-reassignment-reservation-and-resolution-policy-q02","kind":"decision"},{"text":"How may uniqueness scope, persistence, reassignment, reservation and resolution policy be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"uniqueness-scope-persistence-reassignment-reservation-and-resolution-policy-q03","kind":"exception"}]}]}]},{"id":"entry-subject-identifiers-and-classification","name":"Entry, subject, identifiers and classification","description":"Anchors a minimal registry entry to an external subject and its governed identifiers.","layers":[{"id":"entry-identity-subject-reference-and-type","name":"Entry identity, subject reference and type","description":"Defines the anchor and what kind of subject it denotes without copying the subject profile.","findings":[{"id":"entry-id-register-ref-status-created-time-and-head-revision","name":"Entry ID, register reference, status, created time and head revision","description":"Register-qualified entry ID, immutable creation event, current derived status, revision head, predecessor and tombstone or redirect state.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define entry id, register reference, status, created time and head revision?","id":"entry-id-register-ref-status-created-time-and-head-revision-q01","kind":"ownership"},{"text":"Which source, evidence, event time, effective time and knowledge time support entry id, register reference, status, created time and head revision?","id":"entry-id-register-ref-status-created-time-and-head-revision-q02","kind":"provenance"},{"text":"How may entry id, register reference, status, created time and head revision be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"entry-id-register-ref-status-created-time-and-head-revision-q03","kind":"privacy"}]},{"id":"subject-master-reference-kind-classification-and-distinguishing-boundary","name":"Subject master reference, kind, classification and distinguishing boundary","description":"External subject master and kind, classification scheme and version, class criteria, part-whole boundary and minimum distinguishing features.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define subject master reference, kind, classification and distinguishing boundary?","id":"subject-master-reference-kind-classification-and-distinguishing-boundary-q01","kind":"classification"},{"text":"Which source, evidence, event time, effective time and knowledge time support subject master reference, kind, classification and distinguishing boundary?","id":"subject-master-reference-kind-classification-and-distinguishing-boundary-q02","kind":"quality"},{"text":"How may subject master reference, kind, classification and distinguishing boundary be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"subject-master-reference-kind-classification-and-distinguishing-boundary-q03","kind":"security"}]}]},{"id":"identifier-bindings-aliases-and-minimal-labels","name":"Identifier bindings, aliases and minimal labels","description":"Records identifiers and discovery aids as evidence-bearing bindings rather than subject truth.","findings":[{"id":"identifier-binding-scheme-value-canonical-value-status-and-validity","name":"Identifier binding, scheme, value, canonical value, status and validity","description":"Binding identity, scheme and namespace, original and canonical value, assignment authority, binding status, valid interval, predecessor and successor.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define identifier binding, scheme, value, canonical value, status and validity?","id":"identifier-binding-scheme-value-canonical-value-status-and-validity-q01","kind":"composition"},{"text":"Which source, evidence, event time, effective time and knowledge time support identifier binding, scheme, value, canonical value, status and validity?","id":"identifier-binding-scheme-value-canonical-value-status-and-validity-q02","kind":"measurement"},{"text":"How may identifier binding, scheme, value, canonical value, status and validity be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"identifier-binding-scheme-value-canonical-value-status-and-validity-q03","kind":"validation"}]},{"id":"alias-name-locator-language-purpose-source-and-disclosure","name":"Alias, name, locator, language, purpose, source and disclosure","description":"Typed alias, display label or locator with language, audience, purpose, source, effective interval, sensitivity and explicit non-identity semantics.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define alias, name, locator, language, purpose, source and disclosure?","id":"alias-name-locator-language-purpose-source-and-disclosure-q01","kind":"state"},{"text":"Which source, evidence, event time, effective time and knowledge time support alias, name, locator, language, purpose, source and disclosure?","id":"alias-name-locator-language-purpose-source-and-disclosure-q02","kind":"lifecycle"},{"text":"How may alias, name, locator, language, purpose, source and disclosure be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"alias-name-locator-language-purpose-source-and-disclosure-q03","kind":"retention"}]}]}]},{"id":"assignment-proofing-evidence-and-assurance","name":"Assignment, proofing, evidence and assurance","description":"Explains why an entry and identifier binding may be relied upon for a stated purpose.","layers":[{"id":"registration-assignment-and-binding-evidence","name":"Registration, assignment and binding evidence","description":"Captures source-qualified evidence and authority for entry creation and identifier binding.","findings":[{"id":"registration-request-registrar-authority-method-and-decision-evidence","name":"Registration request, registrar authority, method and decision evidence","description":"Request identity, applicant or source reference, registrar and delegation, method, policy version, evidence refs, decision, reason and event time.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define registration request, registrar authority, method and decision evidence?","id":"registration-request-registrar-authority-method-and-decision-evidence-q01","kind":"identity"},{"text":"Which source, evidence, event time, effective time and knowledge time support registration request, registrar authority, method and decision evidence?","id":"registration-request-registrar-authority-method-and-decision-evidence-q02","kind":"evidence"},{"text":"How may registration request, registrar authority, method and decision evidence be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"registration-request-registrar-authority-method-and-decision-evidence-q03","kind":"validation"}]},{"id":"identifier-assignment-source-document-attestation-and-integrity-evidence","name":"Identifier assignment, source document, attestation and integrity evidence","description":"Assignment event, issuing authority, source document or credential reference, attestation, digest, custody, verification result and disclosure marking.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define identifier assignment, source document, attestation and integrity evidence?","id":"identifier-assignment-source-document-attestation-and-integrity-evidence-q01","kind":"definition"},{"text":"Which source, evidence, event time, effective time and knowledge time support identifier assignment, source document, attestation and integrity evidence?","id":"identifier-assignment-source-document-attestation-and-integrity-evidence-q02","kind":"authority"},{"text":"How may identifier assignment, source document, attestation and integrity evidence be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"identifier-assignment-source-document-attestation-and-integrity-evidence-q03","kind":"interoperability"}]}]},{"id":"assurance-quality-conflict-and-observation","name":"Assurance, quality, conflict and observation","description":"Makes uncertainty and disagreement visible at assertion level.","findings":[{"id":"assurance-level-basis-scope-confidence-freshness-and-reassessment","name":"Assurance level, basis, scope, confidence, freshness and reassessment","description":"Named assurance framework and level, assessed assertion, proofing or validation basis, confidence, residual risk, assessment and expiry time.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define assurance level, basis, scope, confidence, freshness and reassessment?","id":"assurance-level-basis-scope-confidence-freshness-and-reassessment-q01","kind":"relationship"},{"text":"Which source, evidence, event time, effective time and knowledge time support assurance level, basis, scope, confidence, freshness and reassessment?","id":"assurance-level-basis-scope-confidence-freshness-and-reassessment-q02","kind":"temporal"},{"text":"How may assurance level, basis, scope, confidence, freshness and reassessment be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"assurance-level-basis-scope-confidence-freshness-and-reassessment-q03","kind":"access"}]},{"id":"quality-rule-validation-result-conflict-contest-and-redress","name":"Quality rule, validation result, conflict, contest and redress","description":"Rule and version, result and errors, conflicting assertions, reporter, subject contest, redress case, resolution authority and preserved outcome.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define quality rule, validation result, conflict, contest and redress?","id":"quality-rule-validation-result-conflict-contest-and-redress-q01","kind":"requirement"},{"text":"Which source, evidence, event time, effective time and knowledge time support quality rule, validation result, conflict, contest and redress?","id":"quality-rule-validation-result-conflict-contest-and-redress-q02","kind":"decision"},{"text":"How may quality rule, validation result, conflict, contest and redress be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"quality-rule-validation-result-conflict-contest-and-redress-q03","kind":"exception"}]}]}]},{"id":"lifecycle-resolution-and-entity-resolution","name":"Lifecycle, resolution and entity resolution","description":"Maintains durable identity through change and provides safe, attributable lookup.","layers":[{"id":"entry-and-binding-lifecycle","name":"Entry and binding lifecycle","description":"Separates entry continuity from each identifier binding and external subject lifecycle.","findings":[{"id":"register-activate-suspend-reactivate-revoke-retire-and-expire-events","name":"Register, activate, suspend, reactivate, revoke, retire and expire events","description":"Typed event, target entry or binding, prior and next state, authority, reason, effective time, observation time, reversibility and evidence.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define register, activate, suspend, reactivate, revoke, retire and expire events?","id":"register-activate-suspend-reactivate-revoke-retire-and-expire-events-q01","kind":"ownership"},{"text":"Which source, evidence, event time, effective time and knowledge time support register, activate, suspend, reactivate, revoke, retire and expire events?","id":"register-activate-suspend-reactivate-revoke-retire-and-expire-events-q02","kind":"provenance"},{"text":"How may register, activate, suspend, reactivate, revoke, retire and expire events be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"register-activate-suspend-reactivate-revoke-retire-and-expire-events-q03","kind":"privacy"}]},{"id":"correction-supersession-tombstone-redirect-and-non-reuse","name":"Correction, supersession, tombstone, redirect and non-reuse","description":"Non-destructive correction, successor relation, tombstone and redirect response, identifier quarantine or non-reuse and retained minimum evidence.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define correction, supersession, tombstone, redirect and non-reuse?","id":"correction-supersession-tombstone-redirect-and-non-reuse-q01","kind":"classification"},{"text":"Which source, evidence, event time, effective time and knowledge time support correction, supersession, tombstone, redirect and non-reuse?","id":"correction-supersession-tombstone-redirect-and-non-reuse-q02","kind":"quality"},{"text":"How may correction, supersession, tombstone, redirect and non-reuse be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"correction-supersession-tombstone-redirect-and-non-reuse-q03","kind":"security"}]}]},{"id":"matching-deduplication-merge-split-and-resolution","name":"Matching, deduplication, merge, split and resolution","description":"Records entity-resolution claims and lookup outcomes without hiding uncertainty.","findings":[{"id":"candidate-match-features-method-score-threshold-and-human-or-authority-review","name":"Candidate match, features, method, score, threshold and authority review","description":"Candidate entries, privacy-safe features, matching method and version, score and scale, threshold, uncertainty, reviewer and disposition.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define candidate match, features, method, score, threshold and authority review?","id":"candidate-match-features-method-score-threshold-and-human-or-authority-review-q01","kind":"composition"},{"text":"Which source, evidence, event time, effective time and knowledge time support candidate match, features, method, score, threshold and authority review?","id":"candidate-match-features-method-score-threshold-and-human-or-authority-review-q02","kind":"measurement"},{"text":"How may candidate match, features, method, score, threshold and authority review be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"candidate-match-features-method-score-threshold-and-human-or-authority-review-q03","kind":"validation"}]},{"id":"equivalence-relatedness-merge-split-survivor-lineage-and-resolution-result","name":"Equivalence, relatedness, merge, split, survivor, lineage and resolution result","description":"Typed same-subject or related assertion, evidence and authority, merge survivor, split children, lineage, redirect and scoped resolver result.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define equivalence, relatedness, merge, split, survivor, lineage and resolution result?","id":"equivalence-relatedness-merge-split-survivor-lineage-and-resolution-result-q01","kind":"state"},{"text":"Which source, evidence, event time, effective time and knowledge time support equivalence, relatedness, merge, split, survivor, lineage and resolution result?","id":"equivalence-relatedness-merge-split-survivor-lineage-and-resolution-result-q02","kind":"lifecycle"},{"text":"How may equivalence, relatedness, merge, split, survivor, lineage and resolution result be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"equivalence-relatedness-merge-split-survivor-lineage-and-resolution-result-q03","kind":"retention"}]}]}]},{"id":"federation-mapping-interoperability-and-projections","name":"Federation, mapping, interoperability and projections","description":"Connects registers while preserving authority, ambiguity and information loss.","layers":[{"id":"cross-register-federation-and-mapping","name":"Cross-register federation and mapping","description":"Pins remote authority, trust and matching semantics for every link.","findings":[{"id":"federation-participant-trust-policy-namespace-and-resolution-contract","name":"Federation participant, trust policy, namespace and resolution contract","description":"Remote register and operator, trust and acceptance policy, supported namespaces, resolver endpoint, authentication, freshness and failure behavior.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define federation participant, trust policy, namespace and resolution contract?","id":"federation-participant-trust-policy-namespace-and-resolution-contract-q01","kind":"identity"},{"text":"Which source, evidence, event time, effective time and knowledge time support federation participant, trust policy, namespace and resolution contract?","id":"federation-participant-trust-policy-namespace-and-resolution-contract-q02","kind":"evidence"},{"text":"How may federation participant, trust policy, namespace and resolution contract be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"federation-participant-trust-policy-namespace-and-resolution-contract-q03","kind":"validation"}]},{"id":"cross-register-mapping-relation-scope-confidence-validity-and-conflict","name":"Cross-register mapping, relation, scope, confidence, validity and conflict","description":"Local and remote entries or identifiers, relation type, mapping authority, scope, method, confidence, valid interval, conflict and revocation.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define cross-register mapping, relation, scope, confidence, validity and conflict?","id":"cross-register-mapping-relation-scope-confidence-validity-and-conflict-q01","kind":"definition"},{"text":"Which source, evidence, event time, effective time and knowledge time support cross-register mapping, relation, scope, confidence, validity and conflict?","id":"cross-register-mapping-relation-scope-confidence-validity-and-conflict-q02","kind":"authority"},{"text":"How may cross-register mapping, relation, scope, confidence, validity and conflict be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"cross-register-mapping-relation-scope-confidence-validity-and-conflict-q03","kind":"interoperability"}]}]},{"id":"standard-crosswalk-and-purpose-bound-views","name":"Standard crosswalk and purpose-bound views","description":"Publishes interoperable projections without overstating equivalence.","findings":[{"id":"iso-nist-did-cid-vc-gs1-lei-crosswalk-and-loss-accounting","name":"ISO, NIST, DID, CID, VC, GS1 and LEI crosswalk and loss accounting","description":"Source and target profile versions, mapped concepts and fields, normalization, omissions, collisions, semantic conflicts and round-trip classification.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define iso, nist, did, cid, vc, gs1 and lei crosswalk and loss accounting?","id":"iso-nist-did-cid-vc-gs1-lei-crosswalk-and-loss-accounting-q01","kind":"relationship"},{"text":"Which source, evidence, event time, effective time and knowledge time support iso, nist, did, cid, vc, gs1 and lei crosswalk and loss accounting?","id":"iso-nist-did-cid-vc-gs1-lei-crosswalk-and-loss-accounting-q02","kind":"temporal"},{"text":"How may iso, nist, did, cid, vc, gs1 and lei crosswalk and loss accounting be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"iso-nist-did-cid-vc-gs1-lei-crosswalk-and-loss-accounting-q03","kind":"access"}]},{"id":"public-relying-party-registrar-subject-self-and-analytical-projection","name":"Public, relying-party, registrar, subject-self and analytical projection","description":"Audience, purpose, legal or policy authority, included fields, redactions, pseudonymization, freshness, expiry and disclosure event.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define public, relying-party, registrar, subject-self and analytical projection?","id":"public-relying-party-registrar-subject-self-and-analytical-projection-q01","kind":"requirement"},{"text":"Which source, evidence, event time, effective time and knowledge time support public, relying-party, registrar, subject-self and analytical projection?","id":"public-relying-party-registrar-subject-self-and-analytical-projection-q02","kind":"decision"},{"text":"How may public, relying-party, registrar, subject-self and analytical projection be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"public-relying-party-registrar-subject-self-and-analytical-projection-q03","kind":"exception"}]}]}]},{"id":"rights-privacy-access-retention-and-agent-governance","name":"Rights, privacy, access, retention and agent governance","description":"Controls identity data and autonomous change across its full lifetime.","layers":[{"id":"purpose-access-privacy-and-subject-rights","name":"Purpose, access, privacy and subject rights","description":"Makes every use and disclosure accountable and contestable.","findings":[{"id":"purpose-legal-basis-consent-access-grant-exception-and-disclosure-log","name":"Purpose, legal basis, consent, access grant, exception and disclosure log","description":"Purpose and authority, consent or alternative basis, actor and role, allowed bundle or finding, conditions, expiry, exception and minimum disclosure receipt.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define purpose, legal basis, consent, access grant, exception and disclosure log?","id":"purpose-legal-basis-consent-access-grant-exception-and-disclosure-log-q01","kind":"ownership"},{"text":"Which source, evidence, event time, effective time and knowledge time support purpose, legal basis, consent, access grant, exception and disclosure log?","id":"purpose-legal-basis-consent-access-grant-exception-and-disclosure-log-q02","kind":"provenance"},{"text":"How may purpose, legal basis, consent, access grant, exception and disclosure log be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"purpose-legal-basis-consent-access-grant-exception-and-disclosure-log-q03","kind":"privacy"}]},{"id":"subject-notice-access-correction-objection-restriction-portability-and-redress","name":"Subject notice, access, correction, objection, restriction, portability and redress","description":"Applicable right, subject or representative, request, identity verification method, deadline, decision, remedy, appeal and protected evidence.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define subject notice, access, correction, objection, restriction, portability and redress?","id":"subject-notice-access-correction-objection-restriction-portability-and-redress-q01","kind":"classification"},{"text":"Which source, evidence, event time, effective time and knowledge time support subject notice, access, correction, objection, restriction, portability and redress?","id":"subject-notice-access-correction-objection-restriction-portability-and-redress-q02","kind":"quality"},{"text":"How may subject notice, access, correction, objection, restriction, portability and redress be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"subject-notice-access-correction-objection-restriction-portability-and-redress-q03","kind":"security"}]}]},{"id":"retention-audit-and-safe-agent-operations","name":"Retention, audit and safe agent operations","description":"Prevents autonomous maintenance from rewriting identity history or crossing authority boundaries.","findings":[{"id":"retention-class-legal-hold-disposition-tombstone-and-erasure-boundary","name":"Retention class, legal hold, disposition, tombstone and erasure boundary","description":"Record class, retention trigger and duration, legal hold, disposition authority, fields removed, tombstone minimum and proof of completion.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define retention class, legal hold, disposition, tombstone and erasure boundary?","id":"retention-class-legal-hold-disposition-tombstone-and-erasure-boundary-q01","kind":"composition"},{"text":"Which source, evidence, event time, effective time and knowledge time support retention class, legal hold, disposition, tombstone and erasure boundary?","id":"retention-class-legal-hold-disposition-tombstone-and-erasure-boundary-q02","kind":"measurement"},{"text":"How may retention class, legal hold, disposition, tombstone and erasure boundary be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"retention-class-legal-hold-disposition-tombstone-and-erasure-boundary-q03","kind":"validation"}]},{"id":"agent-authority-operation-idempotency-concurrency-validation-rollback-and-audit","name":"Agent authority, operation, idempotency, concurrency, validation, rollback and audit","description":"Agent and delegation, operation, purpose, expected head, idempotency key, pre-write checks, result, post-write checks, recovery and audit event.","questions":[{"text":"What identifiers, authorities, classes, versions, scope and values define agent authority, operation, idempotency, concurrency, validation, rollback and audit?","id":"agent-authority-operation-idempotency-concurrency-validation-rollback-and-audit-q01","kind":"state"},{"text":"Which source, evidence, event time, effective time and knowledge time support agent authority, operation, idempotency, concurrency, validation, rollback and audit?","id":"agent-authority-operation-idempotency-concurrency-validation-rollback-and-audit-q02","kind":"lifecycle"},{"text":"How may agent authority, operation, idempotency, concurrency, validation, rollback and audit be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?","id":"agent-authority-operation-idempotency-concurrency-validation-rollback-and-audit-q03","kind":"retention"}]}]}]}]},"agentConduct":{"may":["Resolve an identifier for a stated purpose and return the minimum attributes.","Propose duplicate candidates with match evidence.","Map identifiers to a federated namespace with lineage.","Report assurance levels attached to a registration."],"mustNot":["Merge two entries on name similarity or match score alone.","Treat a successful lookup as authentication or authorization.","Reassign a retired identifier to a new subject.","Expose resolution results beyond the stated purpose.","Delete entries that legal retention rules require to keep."],"requiresHuman":["Merging or splitting subject entries.","Revoking or suspending an identifier.","Handling a subject rights request such as erasure or correction."]},"ethics":{"considerations":["Wrong merges can attach one person's records to another, with serious consequences.","Central registers enable tracking; purpose limitation and minimisation protect subjects.","People must be able to correct identity errors that block their access to services."],"affectedParties":["Registered subjects","Relying services that resolve identifiers","Register operators and authorities"]},"owners":{"steward":"Dimension identity, owner, registrar, namespace authority and accountable privacy and records stewards","roles":[{"name":"Register owner and namespace authority","responsibilities":["Own mandate, authoritative scope, identifier scheme, uniqueness and resolution contract."]},{"name":"Registrar and evidence verifier","responsibilities":["Create entries and bindings only under approved evidence and proofing rules."]},{"name":"Subject or authorized representative","responsibilities":["Receive notice and exercise applicable access, correction, objection and redress rights."]},{"name":"Identity-resolution steward","responsibilities":["Review duplicates, conflicts, matches, merges and splits and preserve lineage."]},{"name":"Federation and interoperability steward","responsibilities":["Govern cross-register trust, mappings, profile versions and loss accounting."]},{"name":"Privacy, security and records steward","responsibilities":["Control minimization, disclosure, redress, retention, legal hold, disposition and auditability."]},{"name":"Relying party","responsibilities":["Interpret scoped resolution and assurance evidence under external policy without treating it as universal truth."]}],"masterSystems":[]},"relations":[{"target":"Person, Organization, Device, Service and Thing models","type":"references","note":"Resolve the subject without copying its profile or lifecycle."},{"target":"Credential, Account, Authentication, Key, Policy and Source Document models","type":"references","note":"Use external proof, control and decision evidence while preserving responsibility boundaries."},{"target":"ISO/IEC 24760-1 and NIST SP 800-63-4","type":"aligned","note":"Align identity vocabulary, proofing, assurance, federation, risk, privacy and redress concepts."},{"target":"DID Core, Controlled Identifiers and Verifiable Credentials","type":"aligned","note":"Project controlled identifiers, controller and resolution data and credential evidence without universalizing their trust model."},{"target":"GS1 Digital Link and GLEIF LEI formats","type":"aligned","note":"Support product, asset, location and legal-entity identifier profiles with explicit scope and loss accounting."},{"target":"PROV-O, RFC 3986, RFC 9562 and RFC 3339","type":"aligned","note":"Represent provenance, identifiers, local UUIDs and explicit event times."},{"target":"Person, Organization, Device, Service or Thing","type":"neighbor","note":"The register stores a minimal external subject reference and identity assertions; each subject model owns descriptive, physical, functional and contextual properties."},{"target":"Credential / Attestation","type":"neighbor","note":"A credential owns issuer claims and validity; the register may cite it as evidence without becoming its issuer, holder or status list."},{"target":"Account / Authentication / Key","type":"neighbor","note":"An entry or identifier can be linked to an account, authenticator or controlled identifier, but lookup does not prove possession or authorize access."},{"target":"Entity Resolution / Master Data","type":"neighbor","note":"This pattern records identity-specific candidate matches, equivalence and lineage; descriptive golden-record consolidation remains in domain master-data models."},{"target":"Authorization / Decision / Audit Log","type":"neighbor","note":"Resolution and assurance are evidence for external decisions, while the model keeps identity-specific provenance and delegates generic logging and authorization."}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system register and entry identifiers qualified by namespace and operator.","Governed globally resolvable URI or sector identifier under a named scheme authority.","Dimension UUID under RFC 9562 when no external or governed global identifier exists."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["A register entry has a namespace, an identifier, a subject type, a registration authority and a lifecycle state.","It is confused with the subject profile, an account, a credential or a master data record."]},"capabilities":{"applicability":"required","items":["Establish register and namespace: Create the governed register profile, authority, subject scope, identifier scheme and resolution rules.","Register subject anchor: Create a minimal entry that references an external subject master under evidenced registrar authority.","Assign or bind identifier: Mint or bind a scheme-governed identifier to an existing entry with explicit validity and source.","Resolve identifier purpose-bound: Resolve an identifier to the minimum permitted current projection while preserving ambiguity and source state.","Attach evidence and assess assurance: Append proofing, assignment or verification evidence and a scope-qualified assurance assessment.","Record match or equivalence assertion: Record candidate similarity, same-subject, related or not-same decisions without changing entry identity.","Merge, split, correct or supersede: Apply an authorized, evidenced lineage change while preserving prior entries, identifiers and redirects.","Suspend, revoke, retire or reactivate: Append a status transition to an entry or binding with reason, authority and effective time.","Federate, map and project: Create a scoped cross-register mapping or standards projection with explicit trust and loss accounting.","Exercise rights, retain, dispose and audit: Process correction or redress and authorized retention or disposition without destroying required lineage."]},"hazards":{"applicability":"required","items":["Identity fusion of different subjects.","Identity theft through weak registration evidence.","Broken references when identifiers are reused or not superseded properly."]},"interfaces":{"applicability":"required","items":["ISO/IEC 24760 framework for identity management.","NIST SP 800-63 digital identity guidelines.","W3C Decentralized Identifiers (DIDs) 1.0.","GLEIF Legal Entity Identifier (ISO 17442).","SCIM 2.0 (IETF RFC 7643 and 7644)."]},"context":{"applicability":"required","items":["Legal identity, identifier validity, subject rights, proofing evidence, retention and redress depend on jurisdiction and sector.","NIST guidance primarily addresses persons using online services and does not establish a universal person, device or thing register.","GS1 and GLEIF define domain identifier systems; their authority and semantics must not be generalized beyond their registered subjects and rules."]}},"sources":[{"title":"Information security, cybersecurity and privacy protection - A framework for identity management - Part 1: Core concepts and terminology","url":"https://www.iso.org/standard/24760-1?browse=tc","note":"International Organization for Standardization and International Electrotechnical Commission"},{"title":"Digital Identity Guidelines","url":"https://pages.nist.gov/800-63-4/sp800-63.html","note":"National Institute of Standards and Technology"},{"title":"Controlled Identifiers v1.0","url":"https://www.w3.org/TR/cid-1.0/","note":"World Wide Web Consortium"},{"title":"Decentralized Identifiers (DIDs) v1.0","url":"https://www.w3.org/TR/did-core/","note":"World Wide Web Consortium"},{"title":"Verifiable Credentials Data Model v2.0","url":"https://www.w3.org/TR/vc-data-model-2.0/","note":"World Wide Web Consortium"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"World Wide Web Consortium"},{"title":"Uniform Resource Identifier (URI): Generic Syntax","url":"https://www.rfc-editor.org/rfc/rfc3986","note":"Internet Engineering Task Force"},{"title":"Universally Unique IDentifiers (UUIDs)","url":"https://www.rfc-editor.org/rfc/rfc9562","note":"Internet Engineering Task Force"},{"title":"Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/rfc/rfc3339","note":"Internet Engineering Task Force"},{"title":"GS1 Digital Link Standard: URI Syntax","url":"https://ref.gs1.org/standards/digital-link/uri-syntax/1.7.0/","note":"GS1"},{"title":"Supporting Documents for LEI Common Data File Formats","url":"https://www.gleif.org/en/lei-data/access-and-use-lei-data/supporting-documents","note":"Global Legal Entity Identifier Foundation"}],"openQuestions":["Licensed full-text clause-level conformity check of ISO/IEC 24760-1:2025 edition 3 against every finding and crosswalk assertion that currently cites SRC-001, replacing catalogue-level attribution with clause-level attribution.","Obtain approved relation rows binding this register to the person, organization, device, service, thing, credential, authentication, authorization, master-data and audit-log models, converting the current composition proposals into contracted, typed relations.","Add a scheme and profile supersession function covering successor profiles, migration maps and preserved old resolver semantics, since the canon and patch rules mandate that behavior but no current function performs it.","Define a field-level redaction and disclosure profile below artifact scope, so deny-by-default minimization can be enforced where a single artifact mixes assertion content with proofing evidence, match features and validation references.","Define a named tombstone-content profile fixing the minimum lawful retained fields after disposition, and prove that non-reuse markers and lineage remnants are not re-identifying correlation handles.","Resolve and document the relationship between W3C Controlled Identifiers v1.0 (SRC-003) and DID Core v1.0 (SRC-004) inside the crosswalk finding, including which controller-document semantics are superseded and what round-trip loss that implies.","Re-derive question kinds semantically per finding and diversify question text, replacing the current fixed eight-finding rotation of the 24-kind taxonomy across three cycles.","Commission the excluded specialist profiles for biometric matching, national civil identity and population registers, eIDAS wallets, sanctions screening and sector-specific eligibility before any of those uses are claimed as in scope.","No independent Claude or Grok result was available; later identity, privacy and jurisdictional review is required before canonical promotion.","No approved relation rows were supplied; relationships to person, organization, device, credential, authentication, authorization, master-data and audit models remain composition proposals.","Biometric matching, national civil identity, population registers, eIDAS wallets, sector-specific eligibility and sanctions screening require separate specialist profiles.","ISO/IEC 24760-1 is represented from the official public catalogue and sample metadata, not a licensed full-text conformity assessment."],"resources":{"spec":"/models/wm-xct-016-identity-register/spec.yaml","agents":"/models/wm-xct-016-identity-register/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-xct-016"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-xct-016-identity-register/spec.yaml","ver-cy/world-models/card-supplements/wm-xct-016-identity-register.json"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-06T04:24:46Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Institutional or informational subject: no invented physical properties.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}