World Models · Published

Identity Register

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.

AI YAMLAGENTS.mdResearch evidence
Published. Research assurance: reviewable-draft. The Codex-only synthesis is published under an explicit repository-owner provider waiver. It passed structural validation and a separate no-tools adversarial audit, but remains a reviewable draft until independent second-provider review and the holds below are closed.
Catalogue IDWM-XCT-016
Version0.3.0-research.1
Previous version-
Typeregistry
ValidationPassed
Synthesis digestsha256:37006e0c028a3c79…
11Sources
6Bundles
12Layers
24Findings
72Questions
24Artifacts
Format-independent logical structure

Bundles → Layers → Findings → Questions + Artifacts

register-authority-namespace-and-schemeRegister authority, namespace and scheme2 layers

Defines the identity register itself and the governed identifier space it operates.

register-identity-mandate-and-profileRegister identity, mandate and profile2 findings

Establishes who operates the register, under what mandate and for which subject domain.

register-identifier-owner-steward-mandate-and-jurisdiction

Register identifier, owner, steward, mandate and jurisdiction

Stable register identity, accountable operator, registrar, steward, legal or policy mandate, jurisdiction and authoritative service references.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define register identifier, owner, steward, mandate and jurisdiction?identity
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support register identifier, owner, steward, mandate and jurisdiction?evidence
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. How may register identifier, owner, steward, mandate and jurisdiction be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?validation
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Register identifier, owner, steward, mandate and jurisdiction recordVersioned evidence-bearing registry record for register identifier, owner, steward, mandate and jurisdiction with authority, event and knowledge time, provenance and disclosure marking.
register-profile-subject-domain-authoritative-scope-and-version

Register profile, subject domain, authoritative scope and version

Profile identity and version, supported subject kinds, authoritative assertions, exclusions, predecessor and compatibility status.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define register profile, subject domain, authoritative scope and version?definition
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support register profile, subject domain, authoritative scope and version?authority
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. How may register profile, subject domain, authoritative scope and version be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?interoperability
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Register profile, subject domain, authoritative scope and version recordVersioned evidence-bearing registry record for register profile, subject domain, authoritative scope and version with authority, event and knowledge time, provenance and disclosure marking.
namespace-scheme-and-identifier-rulesNamespace, scheme and identifier rules2 findings

Makes identifier meaning, comparison and persistence explicit.

namespace-scheme-authority-syntax-canonical-form-and-comparison

Namespace, scheme authority, syntax, canonical form and comparison

Namespace and scheme identifiers, naming authority, grammar, character and case rules, canonical form, parser, validator and equality rules.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define namespace, scheme authority, syntax, canonical form and comparison?relationship
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support namespace, scheme authority, syntax, canonical form and comparison?temporal
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. How may namespace, scheme authority, syntax, canonical form and comparison be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?access
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Namespace, scheme authority, syntax, canonical form and comparison recordVersioned evidence-bearing registry record for namespace, scheme authority, syntax, canonical form and comparison with authority, event and knowledge time, provenance and disclosure marking.
uniqueness-scope-persistence-reassignment-reservation-and-resolution-policy

Uniqueness scope, persistence, reassignment, reservation and resolution policy

Uniqueness domain, minting strategy, collision handling, persistence, non-reuse or reassignment rule, reserved ranges and resolver contract.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define uniqueness scope, persistence, reassignment, reservation and resolution policy?requirement
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support uniqueness scope, persistence, reassignment, reservation and resolution policy?decision
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. How may uniqueness scope, persistence, reassignment, reservation and resolution policy be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?exception
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Uniqueness scope, persistence, reassignment, reservation and resolution policy recordVersioned evidence-bearing registry record for uniqueness scope, persistence, reassignment, reservation and resolution policy with authority, event and knowledge time, provenance and disclosure marking.
entry-subject-identifiers-and-classificationEntry, subject, identifiers and classification2 layers

Anchors a minimal registry entry to an external subject and its governed identifiers.

entry-identity-subject-reference-and-typeEntry identity, subject reference and type2 findings

Defines the anchor and what kind of subject it denotes without copying the subject profile.

entry-id-register-ref-status-created-time-and-head-revision

Entry ID, register reference, status, created time and head revision

Register-qualified entry ID, immutable creation event, current derived status, revision head, predecessor and tombstone or redirect state.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define entry id, register reference, status, created time and head revision?ownership
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support entry id, register reference, status, created time and head revision?provenance
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. 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?privacy
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Entry ID, register reference, status, created time and head revision recordVersioned evidence-bearing registry record for entry id, register reference, status, created time and head revision with authority, event and knowledge time, provenance and disclosure marking.
subject-master-reference-kind-classification-and-distinguishing-boundary

Subject master reference, kind, classification and distinguishing boundary

External subject master and kind, classification scheme and version, class criteria, part-whole boundary and minimum distinguishing features.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define subject master reference, kind, classification and distinguishing boundary?classification
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support subject master reference, kind, classification and distinguishing boundary?quality
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. How may subject master reference, kind, classification and distinguishing boundary be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?security
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Subject master reference, kind, classification and distinguishing boundary recordVersioned evidence-bearing registry record for subject master reference, kind, classification and distinguishing boundary with authority, event and knowledge time, provenance and disclosure marking.
identifier-bindings-aliases-and-minimal-labelsIdentifier bindings, aliases and minimal labels2 findings

Records identifiers and discovery aids as evidence-bearing bindings rather than subject truth.

identifier-binding-scheme-value-canonical-value-status-and-validity

Identifier binding, scheme, value, canonical value, status and validity

Binding identity, scheme and namespace, original and canonical value, assignment authority, binding status, valid interval, predecessor and successor.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define identifier binding, scheme, value, canonical value, status and validity?composition
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support identifier binding, scheme, value, canonical value, status and validity?measurement
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. 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?validation
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Identifier binding, scheme, value, canonical value, status and validity recordVersioned evidence-bearing registry record for identifier binding, scheme, value, canonical value, status and validity with authority, event and knowledge time, provenance and disclosure marking.
alias-name-locator-language-purpose-source-and-disclosure

Alias, name, locator, language, purpose, source and disclosure

Typed alias, display label or locator with language, audience, purpose, source, effective interval, sensitivity and explicit non-identity semantics.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define alias, name, locator, language, purpose, source and disclosure?state
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support alias, name, locator, language, purpose, source and disclosure?lifecycle
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. How may alias, name, locator, language, purpose, source and disclosure be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?retention
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Alias, name, locator, language, purpose, source and disclosure recordVersioned evidence-bearing registry record for alias, name, locator, language, purpose, source and disclosure with authority, event and knowledge time, provenance and disclosure marking.
assignment-proofing-evidence-and-assuranceAssignment, proofing, evidence and assurance2 layers

Explains why an entry and identifier binding may be relied upon for a stated purpose.

registration-assignment-and-binding-evidenceRegistration, assignment and binding evidence2 findings

Captures source-qualified evidence and authority for entry creation and identifier binding.

registration-request-registrar-authority-method-and-decision-evidence

Registration request, registrar authority, method and decision evidence

Request identity, applicant or source reference, registrar and delegation, method, policy version, evidence refs, decision, reason and event time.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define registration request, registrar authority, method and decision evidence?identity
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support registration request, registrar authority, method and decision evidence?evidence
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. How may registration request, registrar authority, method and decision evidence be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?validation
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Registration request, registrar authority, method and decision evidence recordVersioned evidence-bearing registry record for registration request, registrar authority, method and decision evidence with authority, event and knowledge time, provenance and disclosure marking.
identifier-assignment-source-document-attestation-and-integrity-evidence

Identifier assignment, source document, attestation and integrity evidence

Assignment event, issuing authority, source document or credential reference, attestation, digest, custody, verification result and disclosure marking.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define identifier assignment, source document, attestation and integrity evidence?definition
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support identifier assignment, source document, attestation and integrity evidence?authority
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. How may identifier assignment, source document, attestation and integrity evidence be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?interoperability
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Identifier assignment, source document, attestation and integrity evidence recordVersioned evidence-bearing registry record for identifier assignment, source document, attestation and integrity evidence with authority, event and knowledge time, provenance and disclosure marking.
assurance-quality-conflict-and-observationAssurance, quality, conflict and observation2 findings

Makes uncertainty and disagreement visible at assertion level.

assurance-level-basis-scope-confidence-freshness-and-reassessment

Assurance level, basis, scope, confidence, freshness and reassessment

Named assurance framework and level, assessed assertion, proofing or validation basis, confidence, residual risk, assessment and expiry time.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define assurance level, basis, scope, confidence, freshness and reassessment?relationship
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support assurance level, basis, scope, confidence, freshness and reassessment?temporal
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. How may assurance level, basis, scope, confidence, freshness and reassessment be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?access
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Assurance level, basis, scope, confidence, freshness and reassessment recordVersioned evidence-bearing registry record for assurance level, basis, scope, confidence, freshness and reassessment with authority, event and knowledge time, provenance and disclosure marking.
quality-rule-validation-result-conflict-contest-and-redress

Quality rule, validation result, conflict, contest and redress

Rule and version, result and errors, conflicting assertions, reporter, subject contest, redress case, resolution authority and preserved outcome.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define quality rule, validation result, conflict, contest and redress?requirement
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support quality rule, validation result, conflict, contest and redress?decision
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. How may quality rule, validation result, conflict, contest and redress be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?exception
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Quality rule, validation result, conflict, contest and redress recordVersioned evidence-bearing registry record for quality rule, validation result, conflict, contest and redress with authority, event and knowledge time, provenance and disclosure marking.
lifecycle-resolution-and-entity-resolutionLifecycle, resolution and entity resolution2 layers

Maintains durable identity through change and provides safe, attributable lookup.

entry-and-binding-lifecycleEntry and binding lifecycle2 findings

Separates entry continuity from each identifier binding and external subject lifecycle.

register-activate-suspend-reactivate-revoke-retire-and-expire-events

Register, activate, suspend, reactivate, revoke, retire and expire events

Typed event, target entry or binding, prior and next state, authority, reason, effective time, observation time, reversibility and evidence.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define register, activate, suspend, reactivate, revoke, retire and expire events?ownership
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support register, activate, suspend, reactivate, revoke, retire and expire events?provenance
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. 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?privacy
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Register, activate, suspend, reactivate, revoke, retire and expire events recordVersioned evidence-bearing registry record for register, activate, suspend, reactivate, revoke, retire and expire events with authority, event and knowledge time, provenance and disclosure marking.
correction-supersession-tombstone-redirect-and-non-reuse

Correction, supersession, tombstone, redirect and non-reuse

Non-destructive correction, successor relation, tombstone and redirect response, identifier quarantine or non-reuse and retained minimum evidence.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define correction, supersession, tombstone, redirect and non-reuse?classification
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support correction, supersession, tombstone, redirect and non-reuse?quality
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. How may correction, supersession, tombstone, redirect and non-reuse be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?security
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Correction, supersession, tombstone, redirect and non-reuse recordVersioned evidence-bearing registry record for correction, supersession, tombstone, redirect and non-reuse with authority, event and knowledge time, provenance and disclosure marking.
matching-deduplication-merge-split-and-resolutionMatching, deduplication, merge, split and resolution2 findings

Records entity-resolution claims and lookup outcomes without hiding uncertainty.

candidate-match-features-method-score-threshold-and-human-or-authority-review

Candidate match, features, method, score, threshold and authority review

Candidate entries, privacy-safe features, matching method and version, score and scale, threshold, uncertainty, reviewer and disposition.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define candidate match, features, method, score, threshold and authority review?composition
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support candidate match, features, method, score, threshold and authority review?measurement
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. 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?validation
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Candidate match, features, method, score, threshold and authority review recordVersioned evidence-bearing registry record for candidate match, features, method, score, threshold and authority review with authority, event and knowledge time, provenance and disclosure marking.
equivalence-relatedness-merge-split-survivor-lineage-and-resolution-result

Equivalence, relatedness, merge, split, survivor, lineage and resolution result

Typed same-subject or related assertion, evidence and authority, merge survivor, split children, lineage, redirect and scoped resolver result.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define equivalence, relatedness, merge, split, survivor, lineage and resolution result?state
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support equivalence, relatedness, merge, split, survivor, lineage and resolution result?lifecycle
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. 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?retention
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Equivalence, relatedness, merge, split, survivor, lineage and resolution result recordVersioned evidence-bearing registry record for equivalence, relatedness, merge, split, survivor, lineage and resolution result with authority, event and knowledge time, provenance and disclosure marking.
federation-mapping-interoperability-and-projectionsFederation, mapping, interoperability and projections2 layers

Connects registers while preserving authority, ambiguity and information loss.

cross-register-federation-and-mappingCross-register federation and mapping2 findings

Pins remote authority, trust and matching semantics for every link.

federation-participant-trust-policy-namespace-and-resolution-contract

Federation participant, trust policy, namespace and resolution contract

Remote register and operator, trust and acceptance policy, supported namespaces, resolver endpoint, authentication, freshness and failure behavior.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define federation participant, trust policy, namespace and resolution contract?identity
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support federation participant, trust policy, namespace and resolution contract?evidence
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. How may federation participant, trust policy, namespace and resolution contract be validated, contested, corrected, superseded, retained and disclosed without silent merging or expanding authority?validation
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Federation participant, trust policy, namespace and resolution contract recordVersioned evidence-bearing registry record for federation participant, trust policy, namespace and resolution contract with authority, event and knowledge time, provenance and disclosure marking.
cross-register-mapping-relation-scope-confidence-validity-and-conflict

Cross-register mapping, relation, scope, confidence, validity and conflict

Local and remote entries or identifiers, relation type, mapping authority, scope, method, confidence, valid interval, conflict and revocation.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define cross-register mapping, relation, scope, confidence, validity and conflict?definition
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support cross-register mapping, relation, scope, confidence, validity and conflict?authority
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. 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?interoperability
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Cross-register mapping, relation, scope, confidence, validity and conflict recordVersioned evidence-bearing registry record for cross-register mapping, relation, scope, confidence, validity and conflict with authority, event and knowledge time, provenance and disclosure marking.
standard-crosswalk-and-purpose-bound-viewsStandard crosswalk and purpose-bound views2 findings

Publishes interoperable projections without overstating equivalence.

iso-nist-did-cid-vc-gs1-lei-crosswalk-and-loss-accounting

ISO, NIST, DID, CID, VC, GS1 and LEI crosswalk and loss accounting

Source and target profile versions, mapped concepts and fields, normalization, omissions, collisions, semantic conflicts and round-trip classification.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define iso, nist, did, cid, vc, gs1 and lei crosswalk and loss accounting?relationship
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support iso, nist, did, cid, vc, gs1 and lei crosswalk and loss accounting?temporal
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. 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?access
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • ISO, NIST, DID, CID, VC, GS1 and LEI crosswalk and loss accounting recordVersioned evidence-bearing registry record for iso, nist, did, cid, vc, gs1 and lei crosswalk and loss accounting with authority, event and knowledge time, provenance and disclosure marking.
public-relying-party-registrar-subject-self-and-analytical-projection

Public, relying-party, registrar, subject-self and analytical projection

Audience, purpose, legal or policy authority, included fields, redactions, pseudonymization, freshness, expiry and disclosure event.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define public, relying-party, registrar, subject-self and analytical projection?requirement
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support public, relying-party, registrar, subject-self and analytical projection?decision
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. 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?exception
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Public, relying-party, registrar, subject-self and analytical projection recordVersioned evidence-bearing registry record for public, relying-party, registrar, subject-self and analytical projection with authority, event and knowledge time, provenance and disclosure marking.
rights-privacy-access-retention-and-agent-governanceRights, privacy, access, retention and agent governance2 layers

Controls identity data and autonomous change across its full lifetime.

purpose-access-privacy-and-subject-rightsPurpose, access, privacy and subject rights2 findings

Makes every use and disclosure accountable and contestable.

subject-notice-access-correction-objection-restriction-portability-and-redress

Subject notice, access, correction, objection, restriction, portability and redress

Applicable right, subject or representative, request, identity verification method, deadline, decision, remedy, appeal and protected evidence.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define subject notice, access, correction, objection, restriction, portability and redress?classification
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support subject notice, access, correction, objection, restriction, portability and redress?quality
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. 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?security
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Subject notice, access, correction, objection, restriction, portability and redress recordVersioned evidence-bearing registry record for subject notice, access, correction, objection, restriction, portability and redress with authority, event and knowledge time, provenance and disclosure marking.
retention-audit-and-safe-agent-operationsRetention, audit and safe agent operations2 findings

Prevents autonomous maintenance from rewriting identity history or crossing authority boundaries.

agent-authority-operation-idempotency-concurrency-validation-rollback-and-audit

Agent authority, operation, idempotency, concurrency, validation, rollback and audit

Agent and delegation, operation, purpose, expected head, idempotency key, pre-write checks, result, post-write checks, recovery and audit event.

Questions
  1. What identifiers, authorities, classes, versions, scope and values define agent authority, operation, idempotency, concurrency, validation, rollback and audit?state
    Expected answer
    • identifiers and authorities
    • classes and profiles
    • versions and scope
    • values and explicit unknowns
  2. Which source, evidence, event time, effective time and knowledge time support agent authority, operation, idempotency, concurrency, validation, rollback and audit?lifecycle
    Expected answer
    • source and authority
    • evidence and method
    • event and effective time
    • observation and knowledge time
    • confidence and assumptions
  3. 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?retention
    Expected answer
    • validation
    • contest and redress
    • successor history
    • retention and access
    • authority boundary
Artifacts
  • Agent authority, operation, idempotency, concurrency, validation, rollback and audit recordVersioned evidence-bearing registry record for agent authority, operation, idempotency, concurrency, validation, rollback and audit with authority, event and knowledge time, provenance and disclosure marking.

Publication holds

  • Live source and version verification hold: all eleven URLs must be re-fetched and pinned before canonical promotion, with specific attention to SRC-001 (ISO/IEC 24760-1:2025 edition 3, currently represented from catalogue and sample metadata only), SRC-010 (GS1 Digital Link URI Syntax release 1.7.0 and its claimed August 2026 ratification) and SRC-011 (GLEIF common data file supporting documents, cited only by an access date rather than a version).
  • Absence-of-independent-review hold: the repository owner authorized completion with Claude and Grok waived, so this result carries no second-provider corroboration and no external adversarial review. Every publication artifact must display the waiver, the recorded reasons and the reviewable-draft status, and must not be represented as cross-provider validated.
  • Entry-kind reclassification hold: publication must carry the corrected subject-model kind `registry` in place of `pattern`, and must state both axes explicitly so the record-plane classification of the model artifact is never read as the subject-model entry kind.
  • Unapproved-relations hold: relationships to person, organization, device, service, thing, credential, account, key, authorization, master-data and audit-log models must be published as composition proposals with a visible label, since no approved relation rows exist and the coverage checklist contradicts itself on this point.
  • Research-quality caveat hold: the artifact must disclose that all 24 findings share three templated question stems and that question-kind labels are assigned by a fixed rotation rather than by meaning, so taxonomy coverage counts must not be cited as evidence of interrogation depth.
  • Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft.

Deferred research

  • 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.