# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T15:27:18Z", "synthesisSha256": "7efbb56d282ded995b634c914b12a0b9a915d9d27f61767e06cef7b6e0b84f58", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-PER-006", "registryId": "vr.wm-per-006", "name": "Life Event / Civil Status", "version": "0.3.0", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.PER.CIV" ], "tags": [ "life", "event", "civil", "status", "soc.per.civ" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-per-006-life-event-civil-status/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-per-006", "model": { "registry_id": "vr.wm-per-006", "model_id": "WM-PER-006", "name": "Life Event / Civil Status", "entry_kind": "aggregate", "purpose": "Maintain an evidence-qualified civil-status dossier linking a subject to life events, registrations, status assertions and certifications.", "scope_statement": "One locally governed dossier for one subject reference and a declared civil-status jurisdiction/profile. It groups references and assertions over time, including unregistered, incomplete and disputed events. It is not a person master, a civil register, a certificate issuer or a legal status determination engine. Separate dossier identities can coexist for different jurisdictions; no globally unique current status is inferred.", "in_scope": [ "Dossier identity, subject resolution, profile and custodian authority", "Birth, death, union and selected civil-change assertions with registration and evidence references", "Jurisdiction-qualified status assessments, corrections, certificate references, recognition and controlled projections" ], "out_of_scope": [ "Person and identity master lifecycle, registry infrastructure, medical determination, family relationship master and court case management", "Issuing certificates, registering events, changing legal status, deciding recognition, granting nationality or computing benefit eligibility", "Universal legal classifications, statutory deadlines, archival release periods or executable status derivation" ], "boundary_notes": [ { "neighbor": "WM-PER-001 Person", "distinction": "Subject and other participants remain separately mastered; unresolved subject linkage is allowed and does not erase an event or deny personhood.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "WM-XCT-013 Registry Pattern and WM-XCT-016 Identity Register", "distinction": "The dossier references civil entries and identity anchors; it is not a registry specialization and does not create or retire identity masters.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "WM-XCT-017 Attestation / Credential", "distinction": "Certificates retain issuer, issuance identity and scope separate from an event or entry; the dossier only indexes attestations.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006" ] }, { "neighbor": "WM-XCT-015 Event Register and WM-POL-012 Public Benefit / Program", "distinction": "Optional audit/notification and downstream review references do not mandate publication or grant benefit rights. Generic logs and decisions remain external.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ] }, { "neighbor": "Legacy B12 and unreviewed supplement", "distinction": "Reconciled as leads. Reject registration-only civil effect, automatic person existence/retirement, mandatory one-to-one entry links, global status computation and automatic public event logging.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Principles and Recommendations for a Vital Statistics System, Revision 3", "organization": "United Nations Statistics Division", "url": "https://unstats.un.org/unsd/demographic/standmeth/principles/m19rev3en.pdf", "version_or_date": "2014, ST/ESA/STAT/SER.M/19/Rev.3", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T15:25:34Z", "relevance": "Selected definitions and civil registration guidance, including late registration, confidentiality and registration records; not a universal substantive civil law." }, { "id": "SRC-002", "title": "Convention on the Rights of the Child", "organization": "United Nations Children's Fund", "url": "https://www.unicef.org/child-rights-convention/convention-text", "version_or_date": "1989 treaty, Articles 7 and 8; official reproduced text", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T15:25:34Z", "relevance": "Birth registration and identity rights; lack of registration is not a reason to model a child as nonexistent." }, { "id": "SRC-003", "title": "Convention Abolishing the Requirement of Legalisation for Foreign Public Documents", "organization": "Hague Conference on Private International Law", "url": "https://www.hcch.net/en/instruments/conventions/full-text/?cid=41", "version_or_date": "5 October 1961, Articles 1-5", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T15:25:34Z", "relevance": "Authentication formalities within treaty scope, distinct from content truth and legal-effect recognition." }, { "id": "SRC-004", "title": "Regulation (EU) 2016/1191", "organization": "European Parliament and Council of the European Union", "url": "https://eur-lex.europa.eu/eli/reg/2016/1191/oj/eng", "version_or_date": "6 July 2016, selected indexed recital 18; current consolidated applicability unverified", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T15:25:34Z", "relevance": "Selected evidence for separating document circulation from legal effects; full text was not retrieved in the browser." }, { "id": "SRC-005", "title": "Public documents", "organization": "European Commission", "url": "https://e-justice.europa.eu/topics/your-rights/public-documents_en", "version_or_date": "Page last update shown as 05/11/2025; read 2026-10-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T15:25:34Z", "relevance": "EU presentation, translation and authenticity checks; recognition of effects remains a separate assessment under applicable law." }, { "id": "SRC-006", "title": "Correct a birth registration: What corrections can be made", "organization": "General Register Office", "url": "https://www.gov.uk/correct-birth-registration", "version_or_date": "Live guidance read 2026-10-06; England and Wales scope", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T15:25:34Z", "relevance": "A concrete correction example retains original information and adds an authorized annotation; not a worldwide retention rule." }, { "id": "SRC-007", "title": "General Data Protection Regulation", "organization": "European Parliament and Council of the European Union", "url": "https://eur-lex.europa.eu/eli/reg/2016/679", "version_or_date": "Regulation (EU) 2016/679; selected indexed Articles 5 and 6; full current text unverified", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T15:25:34Z", "relevance": "Regional examples of purpose limitation, storage limitation and lawful public-authority processing. Application and exceptions need qualified review." }, { "id": "SRC-008", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T15:25:34Z", "relevance": "Attribution, derivation and revision references for dossier assertions, without certifying their truth." }, { "id": "SRC-009", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "RFC 3339, July 2002, section 5.6", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T15:25:34Z", "relevance": "Timestamp serialization with seconds and offset; civil dates and uncertain event times require separate precision metadata." } ], "structure": { "bundles": [ { "id": "bundle-scope", "name": "Dossier scope and stewardship", "description": "Dossier identity and a declared profile bound every assertion.", "rationale": "Authored dossier organization grounded in the cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-identity", "name": "Dossier identity", "description": "Keep the dossier key distinct from person, event and register-entry identifiers. Unresolved references and possible duplicates require review rather than similarity-based merging.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "findings": [ { "id": "finding-identity", "name": "Subject and dossier resolution", "description": "Keep the dossier key distinct from person, event and register-entry identifiers. Unresolved references and possible duplicates require review rather than similarity-based merging.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "questions": [ { "id": "q-identity-1", "text": "Which opaque dossier key and namespace identify this subject-scoped record?", "kind": "identity", "answer_data": [ "dossier_id, namespace, revision, alias_evidence", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-identity-2", "text": "Which subject and participant references are resolved, provisional or disputed?", "kind": "relationship", "answer_data": [ "subject_ref, participant_refs, resolution_state, assessment_ref", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-identity-3", "text": "What evidence distinguishes a duplicate dossier from distinct people or events?", "kind": "quality", "answer_data": [ "candidate_match_refs, distinguishing_evidence, reviewer, unresolved_reason", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-identity-1", "name": "Dossier identity answer group 1", "description": "Proposed nested fields: dossier_id, namespace, revision, alias_evidence. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "data-identity-2", "name": "Dossier identity answer group 2", "description": "Proposed nested fields: subject_ref, participant_refs, resolution_state, assessment_ref. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "data-identity-3", "name": "Dossier identity answer group 3", "description": "Proposed nested fields: candidate_match_refs, distinguishing_evidence, reviewer, unresolved_reason. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-identity", "name": "Dossier identity evidence index", "description": "Versioned local assertion and external-reference index; not an authoritative certificate or civil register.", "media_or_form": [ "structured index", "authorized dossier view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first; verified external URI next; otherwise local opaque UUID plus revision. Entries keep separate identity from referenced events, documents and persons.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-profile", "name": "Profile and stewardship", "description": "Record jurisdiction, profile version and custodian mandate. Personal involvement alone does not authorize edits to official registers or disclosure of other participants.", "source_refs": [ "SRC-001", "SRC-007" ], "findings": [ { "id": "finding-profile", "name": "Applicable scope and responsible roles", "description": "Record jurisdiction, profile version and custodian mandate. Personal involvement alone does not authorize edits to official registers or disclosure of other participants.", "source_refs": [ "SRC-001", "SRC-007" ], "questions": [ { "id": "q-profile-1", "text": "Which event categories and civil-status dimensions does this jurisdiction profile cover?", "kind": "classification", "answer_data": [ "profile_ref, version, jurisdiction, category_codes, exclusions", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-profile-2", "text": "What mandate authorizes the custodian to maintain each local assertion?", "kind": "authority", "answer_data": [ "custodian_role, mandate_ref, permitted_actions, review_date", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-profile-3", "text": "Which authority retains each register or certificate master and handles disputes?", "kind": "ownership", "answer_data": [ "master_system_refs, responsible_authorities, dispute_route", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-profile-1", "name": "Profile and stewardship answer group 1", "description": "Proposed nested fields: profile_ref, version, jurisdiction, category_codes, exclusions. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "data-profile-2", "name": "Profile and stewardship answer group 2", "description": "Proposed nested fields: custodian_role, mandate_ref, permitted_actions, review_date. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "data-profile-3", "name": "Profile and stewardship answer group 3", "description": "Proposed nested fields: master_system_refs, responsible_authorities, dispute_route. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-profile", "name": "Profile and stewardship evidence index", "description": "Versioned local assertion and external-reference index; not an authoritative certificate or civil register.", "media_or_form": [ "structured index", "authorized dossier view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first; verified external URI next; otherwise local opaque UUID plus revision. Entries keep separate identity from referenced events, documents and persons.", "source_refs": [ "SRC-001", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-occurrences", "name": "Vital and union events", "description": "Record occurrence evidence without conflating registration and legal effect.", "rationale": "Authored dossier organization grounded in the cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-009" ], "layers": [ { "id": "layer-vital", "name": "Birth and death assertions", "description": "Record separately evidenced birth and death assertions, including missing registration. Do not derive absence of life or personhood from missing documents. Statistical categories are not a medical diagnosis or a universal legal test.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ], "findings": [ { "id": "finding-vital", "name": "Occurrence and registration remain distinct", "description": "Record separately evidenced birth and death assertions, including missing registration. Do not derive absence of life or personhood from missing documents. Statistical categories are not a medical diagnosis or a universal legal test.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ], "questions": [ { "id": "q-vital-1", "text": "What birth or death occurrence is asserted and how is its event category supported?", "kind": "event", "answer_data": [ "event_ref, category, supporting_record_ref, assertion_state", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-vital-2", "text": "Which occurrence place and time are known, approximate or disputed?", "kind": "spatial", "answer_data": [ "place_ref, event_date_or_time, precision, uncertainty, conflicting_assertions", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-vital-3", "text": "Which profile-specific evidence or category review remains unresolved for this occurrence?", "kind": "constraint", "answer_data": [ "review_issue, profile_rule_ref, evidence_gap, escalation_role", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-vital-1", "name": "Birth and death assertions answer group 1", "description": "Proposed nested fields: event_ref, category, supporting_record_ref, assertion_state. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ] }, { "id": "data-vital-2", "name": "Birth and death assertions answer group 2", "description": "Proposed nested fields: place_ref, event_date_or_time, precision, uncertainty, conflicting_assertions. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ] }, { "id": "data-vital-3", "name": "Birth and death assertions answer group 3", "description": "Proposed nested fields: review_issue, profile_rule_ref, evidence_gap, escalation_role. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ] } ], "artifacts": [ { "id": "artifact-vital", "name": "Birth and death assertions evidence index", "description": "Versioned local assertion and external-reference index; not an authoritative certificate or civil register.", "media_or_form": [ "structured index", "authorized dossier view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first; verified external URI next; otherwise local opaque UUID plus revision. Entries keep separate identity from referenced events, documents and persons.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-union", "name": "Union events", "description": "Keep marriage, partnership, separation, dissolution and annulment assertions distinct. Store applicable effect evidence; ordering documents alone does not establish capacity or a status transition.", "source_refs": [ "SRC-001", "SRC-005" ], "findings": [ { "id": "finding-union", "name": "Formation and dissolution references", "description": "Keep marriage, partnership, separation, dissolution and annulment assertions distinct. Store applicable effect evidence; ordering documents alone does not establish capacity or a status transition.", "source_refs": [ "SRC-001", "SRC-005" ], "questions": [ { "id": "q-union-1", "text": "Which union and participant references does this event concern?", "kind": "relationship", "answer_data": [ "union_ref, participant_roles, event_ref, linkage_evidence", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-union-2", "text": "Which formation or termination category is asserted under the relevant profile?", "kind": "classification", "answer_data": [ "category_code, profile_ref, decision_or_act_ref", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-union-3", "text": "Which occurrence and asserted effect dates apply to this union event?", "kind": "temporal", "answer_data": [ "occurrence_date, effective_date, authority_ref, pending_effect_reason", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-union-1", "name": "Union events answer group 1", "description": "Proposed nested fields: union_ref, participant_roles, event_ref, linkage_evidence. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "data-union-2", "name": "Union events answer group 2", "description": "Proposed nested fields: category_code, profile_ref, decision_or_act_ref. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "data-union-3", "name": "Union events answer group 3", "description": "Proposed nested fields: occurrence_date, effective_date, authority_ref, pending_effect_reason. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-union", "name": "Union events evidence index", "description": "Versioned local assertion and external-reference index; not an authoritative certificate or civil register.", "media_or_form": [ "structured index", "authorized dossier view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first; verified external URI next; otherwise local opaque UUID plus revision. Entries keep separate identity from referenced events, documents and persons.", "source_refs": [ "SRC-001", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-change-intake", "name": "Civil changes and registration intake", "description": "Changes and pending reports remain evidenced, scoped assertions.", "rationale": "Authored dossier organization grounded in the cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-changes", "name": "Other civil changes", "description": "Reference evidenced name, parenthood and adoption changes within the selected profile. Historical names and protected family links are not default disclosure fields. Recorded marker changes need separate specialist profiling before use.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007" ], "findings": [ { "id": "finding-changes", "name": "Name and family-status change references", "description": "Reference evidenced name, parenthood and adoption changes within the selected profile. Historical names and protected family links are not default disclosure fields. Recorded marker changes need separate specialist profiling before use.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007" ], "questions": [ { "id": "q-changes-1", "text": "Which civil attribute or family-status assertion is being changed?", "kind": "definition", "answer_data": [ "change_type, affected_assertion_ref, profile_ref", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-changes-2", "text": "What act or decision supports this civil change and its claimed scope?", "kind": "evidence", "answer_data": [ "act_ref, authority_ref, effective_scope, evidence_state", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-changes-3", "text": "Which earlier names or family links require a restricted or sealed reference?", "kind": "privacy", "answer_data": [ "protected_reference, access_rule_ref, permitted_view, redaction_reason", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-changes-1", "name": "Other civil changes answer group 1", "description": "Proposed nested fields: change_type, affected_assertion_ref, profile_ref. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007" ] }, { "id": "data-changes-2", "name": "Other civil changes answer group 2", "description": "Proposed nested fields: act_ref, authority_ref, effective_scope, evidence_state. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007" ] }, { "id": "data-changes-3", "name": "Other civil changes answer group 3", "description": "Proposed nested fields: protected_reference, access_rule_ref, permitted_view, redaction_reason. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-changes", "name": "Other civil changes evidence index", "description": "Versioned local assertion and external-reference index; not an authoritative certificate or civil register.", "media_or_form": [ "structured index", "authorized dossier view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first; verified external URI next; otherwise local opaque UUID plus revision. Entries keep separate identity from referenced events, documents and persons.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-intake", "name": "Notification and delayed registration", "description": "Retain reported occurrences without inventing an official entry. Keep notification, application, registration and delay assessments separate; no universal grace period or penalty is encoded.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "findings": [ { "id": "finding-intake", "name": "Unregistered and pending evidence", "description": "Retain reported occurrences without inventing an official entry. Keep notification, application, registration and delay assessments separate; no universal grace period or penalty is encoded.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "questions": [ { "id": "q-intake-1", "text": "Which report or notification supplied the event assertion?", "kind": "process", "answer_data": [ "report_ref, informant_role, received_at, provenance_ref", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-intake-2", "text": "What is the evidenced registration state and which evidence is still missing?", "kind": "state", "answer_data": [ "registration_state, evidence_needed, entry_ref_if_known, unknown_reason", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-intake-3", "text": "Which applicable rule and circumstances explain a late or delayed registration assessment?", "kind": "exception", "answer_data": [ "rule_ref, trigger_date, registration_date, delay_reason, assessment_ref", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-intake-1", "name": "Notification and delayed registration answer group 1", "description": "Proposed nested fields: report_ref, informant_role, received_at, provenance_ref. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "data-intake-2", "name": "Notification and delayed registration answer group 2", "description": "Proposed nested fields: registration_state, evidence_needed, entry_ref_if_known, unknown_reason. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "data-intake-3", "name": "Notification and delayed registration answer group 3", "description": "Proposed nested fields: rule_ref, trigger_date, registration_date, delay_reason, assessment_ref. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-intake", "name": "Notification and delayed registration evidence index", "description": "Versioned local assertion and external-reference index; not an authoritative certificate or civil register.", "media_or_form": [ "structured index", "authorized dossier view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first; verified external URI next; otherwise local opaque UUID plus revision. Entries keep separate identity from referenced events, documents and persons.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-registration", "name": "Registration continuity", "description": "Entry linkage and corrections preserve authority and disagreement.", "rationale": "Authored dossier organization grounded in the cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-entry", "name": "Register entries", "description": "An event may have no located entry or multiple jurisdictional entries. Preserve differences and transcription links rather than imposing one-to-one global registration identity.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ], "findings": [ { "id": "finding-entry", "name": "Authority-qualified entry linkage", "description": "An event may have no located entry or multiple jurisdictional entries. Preserve differences and transcription links rather than imposing one-to-one global registration identity.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ], "questions": [ { "id": "q-entry-1", "text": "Which register namespace and entry identifier anchor each registration claim?", "kind": "identity", "answer_data": [ "registry_ref, entry_id, registering_authority, entry_revision", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-entry-2", "text": "How was each entry reference obtained and assessed?", "kind": "provenance", "answer_data": [ "source_ref, retrieved_at, assessor, verification_state", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-entry-3", "text": "Which entries are originals, transcriptions or unresolved alternatives for this event?", "kind": "composition", "answer_data": [ "entry_refs, linkage_type, basis_ref, competing_assertions", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-entry-1", "name": "Register entries answer group 1", "description": "Proposed nested fields: registry_ref, entry_id, registering_authority, entry_revision. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "data-entry-2", "name": "Register entries answer group 2", "description": "Proposed nested fields: source_ref, retrieved_at, assessor, verification_state. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "data-entry-3", "name": "Register entries answer group 3", "description": "Proposed nested fields: entry_refs, linkage_type, basis_ref, competing_assertions. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-entry", "name": "Register entries evidence index", "description": "Versioned local assertion and external-reference index; not an authoritative certificate or civil register.", "media_or_form": [ "structured index", "authorized dossier view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first; verified external URI next; otherwise local opaque UUID plus revision. Entries keep separate identity from referenced events, documents and persons.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-correction", "name": "Correction and challenge", "description": "Link a correction request separately from a completed authorized correction. Original records remain externally governed; local supersession does not itself amend, annul or erase a register.", "source_refs": [ "SRC-006", "SRC-007", "SRC-008" ], "findings": [ { "id": "finding-correction", "name": "Revision without silent replacement", "description": "Link a correction request separately from a completed authorized correction. Original records remain externally governed; local supersession does not itself amend, annul or erase a register.", "source_refs": [ "SRC-006", "SRC-007", "SRC-008" ], "questions": [ { "id": "q-correction-1", "text": "Which assertion or entry is challenged, corrected or superseded?", "kind": "lifecycle", "answer_data": [ "affected_ref, challenge_state, superseding_ref, revision", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-correction-2", "text": "What authority and evidence support the recorded correction outcome?", "kind": "authority", "answer_data": [ "decision_ref, authority_ref, outcome_scope, recorded_at", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-correction-3", "text": "Which historical payload remains necessary or restricted after the correction?", "kind": "retention", "answer_data": [ "history_policy_ref, payload_scope, restricted_view, disposition_review", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-correction-1", "name": "Correction and challenge answer group 1", "description": "Proposed nested fields: affected_ref, challenge_state, superseding_ref, revision. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-007", "SRC-008" ] }, { "id": "data-correction-2", "name": "Correction and challenge answer group 2", "description": "Proposed nested fields: decision_ref, authority_ref, outcome_scope, recorded_at. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-007", "SRC-008" ] }, { "id": "data-correction-3", "name": "Correction and challenge answer group 3", "description": "Proposed nested fields: history_policy_ref, payload_scope, restricted_view, disposition_review. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-correction", "name": "Correction and challenge evidence index", "description": "Versioned local assertion and external-reference index; not an authoritative certificate or civil register.", "media_or_form": [ "structured index", "authorized dossier view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first; verified external URI next; otherwise local opaque UUID plus revision. Entries keep separate identity from referenced events, documents and persons.", "source_refs": [ "SRC-006", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-status", "name": "Status and time", "description": "Qualified status assertions retain temporal and jurisdictional context.", "rationale": "Authored dossier organization grounded in the cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008", "SRC-009" ], "layers": [ { "id": "layer-status", "name": "Status assertions", "description": "Keep status dimension, reference period, jurisdiction, authority and evidence together. An attested status may be recorded when its full event chain is unavailable. Such a gap prevents claiming a complete reconstruction, not recording the attestation.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ], "findings": [ { "id": "finding-status", "name": "Jurisdiction-qualified status evidence", "description": "Keep status dimension, reference period, jurisdiction, authority and evidence together. An attested status may be recorded when its full event chain is unavailable. Such a gap prevents claiming a complete reconstruction, not recording the attestation.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ], "questions": [ { "id": "q-status-1", "text": "Which civil-status value is asserted for this jurisdiction and reference period?", "kind": "state", "answer_data": [ "dimension, value, jurisdiction, valid_period, assertion_state", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-status-2", "text": "Which attestation, decision or event evidence supports this status assertion?", "kind": "evidence", "answer_data": [ "evidence_refs, issuing_authority, missing_chain_reason", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-status-3", "text": "What assessment supports acceptance, qualification or dispute of this status view?", "kind": "decision", "answer_data": [ "assessment_ref, assessor_role, rule_version, qualification, decision_time", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-status-1", "name": "Status assertions answer group 1", "description": "Proposed nested fields: dimension, value, jurisdiction, valid_period, assertion_state. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "data-status-2", "name": "Status assertions answer group 2", "description": "Proposed nested fields: evidence_refs, issuing_authority, missing_chain_reason. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "data-status-3", "name": "Status assertions answer group 3", "description": "Proposed nested fields: assessment_ref, assessor_role, rule_version, qualification, decision_time. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-status", "name": "Status assertions evidence index", "description": "Versioned local assertion and external-reference index; not an authoritative certificate or civil register.", "media_or_form": [ "structured index", "authorized dossier view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first; verified external URI next; otherwise local opaque UUID plus revision. Entries keep separate identity from referenced events, documents and persons.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-timeline", "name": "Temporal consistency", "description": "Keep effective, observation and recording times distinct. Concurrent jurisdictional views and backdated corrections may coexist; the newest upload is not automatically the legally relevant status.", "source_refs": [ "SRC-005", "SRC-008", "SRC-009" ], "findings": [ { "id": "finding-timeline", "name": "Incomplete and competing status histories", "description": "Keep effective, observation and recording times distinct. Concurrent jurisdictional views and backdated corrections may coexist; the newest upload is not automatically the legally relevant status.", "source_refs": [ "SRC-005", "SRC-008", "SRC-009" ], "questions": [ { "id": "q-timeline-1", "text": "Which effective intervals and recording instants belong to each status version?", "kind": "temporal", "answer_data": [ "status_ref, valid_from, valid_until, observed_at, recorded_at, precision", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-timeline-2", "text": "Which overlaps or gaps prevent a consistent view for the requested date?", "kind": "validation", "answer_data": [ "overlap_refs, gap_interval, consistency_issue, review_status", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-timeline-3", "text": "How does a retrospective correction affect an earlier projection without rewriting its provenance?", "kind": "exception", "answer_data": [ "correction_ref, prior_projection_ref, revised_view_ref, assessment_basis", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-timeline-1", "name": "Temporal consistency answer group 1", "description": "Proposed nested fields: status_ref, valid_from, valid_until, observed_at, recorded_at, precision. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-008", "SRC-009" ] }, { "id": "data-timeline-2", "name": "Temporal consistency answer group 2", "description": "Proposed nested fields: overlap_refs, gap_interval, consistency_issue, review_status. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-008", "SRC-009" ] }, { "id": "data-timeline-3", "name": "Temporal consistency answer group 3", "description": "Proposed nested fields: correction_ref, prior_projection_ref, revised_view_ref, assessment_basis. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "artifact-timeline", "name": "Temporal consistency evidence index", "description": "Versioned local assertion and external-reference index; not an authoritative certificate or civil register.", "media_or_form": [ "structured index", "authorized dossier view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first; verified external URI next; otherwise local opaque UUID plus revision. Entries keep separate identity from referenced events, documents and persons.", "source_refs": [ "SRC-005", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-certification", "name": "Certification and recognition", "description": "Document identity, authenticity and civil effect are different assessments.", "rationale": "Authored dossier organization grounded in the cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-008" ], "layers": [ { "id": "layer-certificate", "name": "Certificate evidence", "description": "Distinguish entry, issuance, certified copy and local scan. A digest proves neither issuer authority nor current acceptability. Preserve historical evidence without presenting it as a fresh status guarantee.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-008" ], "findings": [ { "id": "finding-certificate", "name": "Issuance identity and presented copies", "description": "Distinguish entry, issuance, certified copy and local scan. A digest proves neither issuer authority nor current acceptability. Preserve historical evidence without presenting it as a fresh status guarantee.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-008" ], "questions": [ { "id": "q-certificate-1", "text": "Which issuer and issuance identifier distinguish this certificate from its source entry?", "kind": "identity", "answer_data": [ "issuer_ref, certificate_id, source_entry_ref, issued_at", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-certificate-2", "text": "What provenance and authenticity assessment accompany the presented copy?", "kind": "evidence", "answer_data": [ "copy_ref, transformation_ref, integrity_digest, authenticity_state", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-certificate-3", "text": "What recipient purpose and profile determine whether this certificate is suitable now?", "kind": "requirement", "answer_data": [ "recipient_purpose, required_form, assessment_date, supersession_or_rejection_reason", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-certificate-1", "name": "Certificate evidence answer group 1", "description": "Proposed nested fields: issuer_ref, certificate_id, source_entry_ref, issued_at. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-008" ] }, { "id": "data-certificate-2", "name": "Certificate evidence answer group 2", "description": "Proposed nested fields: copy_ref, transformation_ref, integrity_digest, authenticity_state. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-008" ] }, { "id": "data-certificate-3", "name": "Certificate evidence answer group 3", "description": "Proposed nested fields: recipient_purpose, required_form, assessment_date, supersession_or_rejection_reason. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-certificate", "name": "Certificate evidence evidence index", "description": "Versioned local assertion and external-reference index; not an authoritative certificate or civil register.", "media_or_form": [ "structured index", "authorized dossier view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first; verified external URI next; otherwise local opaque UUID plus revision. Entries keep separate identity from referenced events, documents and persons.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-recognition", "name": "Cross-jurisdiction use", "description": "Record origin and destination profiles, formalities and recognition evidence separately. Apostilles and translation aids do not decide the substantive civil effects of a foreign event.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ], "findings": [ { "id": "finding-recognition", "name": "Authenticity and legal effects assessed separately", "description": "Record origin and destination profiles, formalities and recognition evidence separately. Apostilles and translation aids do not decide the substantive civil effects of a foreign event.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ], "questions": [ { "id": "q-recognition-1", "text": "Which origin and receiving jurisdictions and document rules govern this presentation?", "kind": "interoperability", "answer_data": [ "origin_jurisdiction, destination_jurisdiction, rule_refs, language_requirements", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-recognition-2", "text": "What evidence supports authenticity or a formalities exemption for this document?", "kind": "validation", "answer_data": [ "authentication_ref, exemption_basis, scope_check, unresolved_doubt", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-recognition-3", "text": "Which competent assessment addresses recognition of the claimed legal effects?", "kind": "authority", "answer_data": [ "recognition_decision_ref, authority, effects_scope, conditions, pending_reason", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-recognition-1", "name": "Cross-jurisdiction use answer group 1", "description": "Proposed nested fields: origin_jurisdiction, destination_jurisdiction, rule_refs, language_requirements. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "data-recognition-2", "name": "Cross-jurisdiction use answer group 2", "description": "Proposed nested fields: authentication_ref, exemption_basis, scope_check, unresolved_doubt. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "data-recognition-3", "name": "Cross-jurisdiction use answer group 3", "description": "Proposed nested fields: recognition_decision_ref, authority, effects_scope, conditions, pending_reason. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-recognition", "name": "Cross-jurisdiction use evidence index", "description": "Versioned local assertion and external-reference index; not an authoritative certificate or civil register.", "media_or_form": [ "structured index", "authorized dossier view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first; verified external URI next; otherwise local opaque UUID plus revision. Entries keep separate identity from referenced events, documents and persons.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-governance", "name": "Disclosure and continuity", "description": "Access, retention and downstream references are purpose-bound.", "rationale": "Authored dossier organization grounded in the cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-disclosure", "name": "Access and projections", "description": "A status-only response still reveals personal information. Scope each local projection to an authorized purpose and retain unknown or contested qualifiers; neither kinship nor an archival date creates blanket access.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "findings": [ { "id": "finding-disclosure", "name": "Purpose-bound minimal views", "description": "A status-only response still reveals personal information. Scope each local projection to an authorized purpose and retain unknown or contested qualifiers; neither kinship nor an archival date creates blanket access.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "questions": [ { "id": "q-disclosure-1", "text": "Which recipient entitlement permits the requested status or event view?", "kind": "access", "answer_data": [ "recipient_role, purpose, entitlement_ref, scope, decision", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-disclosure-2", "text": "Which fields and linked participants must be hidden in this projection?", "kind": "security", "answer_data": [ "field_allowlist, protected_refs, redaction_rule, leakage_review", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-disclosure-3", "text": "Which mapping losses would make a status-only projection misleading?", "kind": "interoperability", "answer_data": [ "target_profile, mapping_version, omitted_qualifiers, refusal_reason", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-disclosure-1", "name": "Access and projections answer group 1", "description": "Proposed nested fields: recipient_role, purpose, entitlement_ref, scope, decision. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "data-disclosure-2", "name": "Access and projections answer group 2", "description": "Proposed nested fields: field_allowlist, protected_refs, redaction_rule, leakage_review. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "data-disclosure-3", "name": "Access and projections answer group 3", "description": "Proposed nested fields: target_profile, mapping_version, omitted_qualifiers, refusal_reason. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-disclosure", "name": "Access and projections evidence index", "description": "Versioned local assertion and external-reference index; not an authoritative certificate or civil register.", "media_or_form": [ "structured index", "authorized dossier view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first; verified external URI next; otherwise local opaque UUID plus revision. Entries keep separate identity from referenced events, documents and persons.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-continuity", "name": "Retention and downstream continuity", "description": "Separate authoritative register preservation from dossier-copy retention. Corrections may require downstream review but never automatic identity retirement, benefit termination or public notification.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ], "findings": [ { "id": "finding-continuity", "name": "Governed copies and dependencies", "description": "Separate authoritative register preservation from dossier-copy retention. Corrections may require downstream review but never automatic identity retirement, benefit termination or public notification.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ], "questions": [ { "id": "q-continuity-1", "text": "Which retention rule, legal hold or lawful disposal decision applies to each local copy?", "kind": "retention", "answer_data": [ "record_class, schedule_ref, hold_ref, review_date, disposition_ref", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-continuity-2", "text": "Which authorized downstream references need review after an evidenced change?", "kind": "relationship", "answer_data": [ "dependency_refs, change_ref, review_request_ref, acknowledgment_state", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] }, { "id": "q-continuity-3", "text": "What evidence is required before this dossier profile can be used operationally?", "kind": "validation", "answer_data": [ "schema_version, legal_review_ref, mapping_tests, unresolved_holds", "Include source reference, assessment state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-continuity-1", "name": "Retention and downstream continuity answer group 1", "description": "Proposed nested fields: record_class, schedule_ref, hold_ref, review_date, disposition_ref. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ] }, { "id": "data-continuity-2", "name": "Retention and downstream continuity answer group 2", "description": "Proposed nested fields: dependency_refs, change_ref, review_request_ref, acknowledgment_state. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ] }, { "id": "data-continuity-3", "name": "Retention and downstream continuity answer group 3", "description": "Proposed nested fields: schema_version, legal_review_ref, mapping_tests, unresolved_holds. Candidate structure requires a typed profile before instance validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-continuity", "name": "Retention and downstream continuity evidence index", "description": "Versioned local assertion and external-reference index; not an authoritative certificate or civil register.", "media_or_form": [ "structured index", "authorized dossier view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first; verified external URI next; otherwise local opaque UUID plus revision. Entries keep separate identity from referenced events, documents and persons.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "resolve-dossier", "name": "Resolve a qualified dossier reference", "description": "Proposed operation, not implemented. Return exact or unresolved subject-scoped references without merging people by name or date.", "inputs": [ "namespace and dossier ID", "authorized purpose" ], "outputs": [ "reference or ambiguity report" ], "preconditions": [ "Verified role, purpose and access scope for every included record", "Applicable profile and evidence identified; unresolved authority causes refusal", "Mutations require current revision and idempotency key; conflicts produce refusal" ], "effects": [ "Read-only resolution; no master identity change" ], "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "record-event-assertion", "name": "Record an evidenced event assertion", "description": "Proposed operation, not implemented. Append a local occurrence assertion while keeping registration and effect unknown unless evidenced.", "inputs": [ "event evidence", "subject and participant refs", "expected revision" ], "outputs": [ "assertion revision or refusal" ], "preconditions": [ "Verified role, purpose and access scope for every included record", "Applicable profile and evidence identified; unresolved authority causes refusal", "Mutations require current revision and idempotency key; conflicts produce refusal" ], "effects": [ "Local assertion appended; no event registration or civil effect created" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "link-registration", "name": "Link a registration reference", "description": "Proposed operation, not implemented. Add an authority-qualified entry reference and its assessment without changing the register.", "inputs": [ "entry reference and evidence", "expected revision" ], "outputs": [ "link revision or refusal" ], "preconditions": [ "Verified role, purpose and access scope for every included record", "Applicable profile and evidence identified; unresolved authority causes refusal", "Mutations require current revision and idempotency key; conflicts produce refusal" ], "effects": [ "Local linkage only; conflicting entries preserved" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "record-status-assessment", "name": "Record an existing status assessment", "description": "Proposed operation, not implemented. Capture an authorized attestation or assessment with its jurisdiction and period. Do not compute legal status from event order.", "inputs": [ "assessment evidence and authority", "jurisdiction and reference period", "expected revision" ], "outputs": [ "qualified status assertion or refusal" ], "preconditions": [ "Verified role, purpose and access scope for every included record", "Applicable profile and evidence identified; unresolved authority causes refusal", "Mutations require current revision and idempotency key; conflicts produce refusal" ], "effects": [ "Local assessment recorded; no rights or official status changed" ], "source_refs": [ "SRC-005", "SRC-008", "SRC-009" ] }, { "id": "link-correction", "name": "Link an authorized correction outcome", "description": "Proposed operation, not implemented. Record a correction or challenge reference and local supersession with restricted history.", "inputs": [ "correction evidence", "affected assertion", "expected revision" ], "outputs": [ "revision links or refusal" ], "preconditions": [ "Verified role, purpose and access scope for every included record", "Applicable profile and evidence identified; unresolved authority causes refusal", "Mutations require current revision and idempotency key; conflicts produce refusal" ], "effects": [ "Local references updated; no register amendment or automatic downstream action" ], "source_refs": [ "SRC-006", "SRC-007", "SRC-008" ] }, { "id": "prepare-projection", "name": "Prepare an authorized dossier projection", "description": "Proposed operation, not implemented. Create a local minimal view with uncertainty and loss report. Refuse disclosure scope or target mappings that cannot preserve required qualifiers.", "inputs": [ "recipient purpose and authority", "dossier revision", "target profile" ], "outputs": [ "local projection and audit reference or refusal" ], "preconditions": [ "Verified role, purpose and access scope for every included record", "Applicable profile and evidence identified; unresolved authority causes refusal", "Mutations require current revision and idempotency key; conflicts produce refusal" ], "effects": [ "Local artifact only; no transmission, certificate issuance or legal recognition" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-008" ] } ], "composition": [ { "target": "WM-PER-001", "relation": "REFERENCE", "purpose": "Candidate person binding; subjects and participants remain separately mastered, including provisional unresolved references.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-XCT-013", "relation": "ALIGN", "purpose": "Candidate registry concepts only; reject legacy EXTEND because the root is a dossier, not the civil register.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "WM-XCT-016", "relation": "REFERENCE", "purpose": "Candidate identity register reference; no automatic birth creation or death retirement of the identity master.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-XCT-017", "relation": "REFERENCE", "purpose": "Candidate attestation binding; certificate issuance and credential lifecycle stay external.", "required": false, "source_refs": [ "SRC-003", "SRC-005", "SRC-006" ] }, { "target": "WM-XCT-015", "relation": "REFERENCE", "purpose": "Optional authorized audit or change-event reference; reject mandatory public log composition.", "required": false, "source_refs": [ "SRC-007", "SRC-008" ] }, { "target": "WM-POL-012", "relation": "REFERENCE", "purpose": "Optional downstream program review reference; no eligibility or entitlement inference.", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "target": "UN CRVS Revision 3", "relation": "ALIGN", "purpose": "Selected concepts only; statistical terminology is not a universal substantive civil law.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "PROV-O 2013", "relation": "ALIGN", "purpose": "Conceptual assertion provenance mapping; no executable conformance claim.", "required": false, "source_refs": [ "SRC-008" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Accountable dossier custodian role and evidenced mandate", "Jurisdiction/profile version, legal basis and disputed-assertion escalation role", "Master namespaces, recipient access policy and copy-specific retention schedule" ], "namespace_guidance": "Use opaque dossier identity distinct from subject and registration identifiers; do not put names or birth dates in identifiers.", "registry_links": [ "vr.wm-per-006", "Optional neighbor bindings need pinned versions and boundary review before use" ] }, "canon_and_patch": { "canonicalization_rules": [ "Retain competing source assertions; do not equate matching names, dates or certificate copies with event identity.", "Keep legal effect, registration state, authenticity and local assessment state distinct." ], "patch_rules": [ "Append provenance, actor, purpose, expected revision and idempotency key; stale revisions fail.", "Preserve lawful supersession references while restricting or disposing personal payload under the applicable schedule." ], "compatibility_rules": [ "Version event/status vocabularies and mappings; refuse targets that drop jurisdiction, uncertainty or access restrictions." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier with namespace and revision", "Governed external URI with version and authority context", "Locally assigned opaque UUID with reconciliation status" ], "timestamp_rule": "Recording and observation instants use RFC 3339 with seconds and explicit UTC offset or Z. Keep event time, registration time, effective time, issuance and ingestion times distinct. Date-only, approximate and unknown values retain their precision and calendar; never fabricate midnight or a known offset.", "serial_naming_rule": "Opaque dossier key, artifact type and sequence or revision; no names, dates of birth or protected family details in filenames.", "integrity_rule": "Record digest algorithm, source and transformation provenance where available. A digest does not prove truth, issuer authority, admissibility or civil effect." }, "policies": [ "Reviewable draft only under the single-provider waiver; source/version and independent-review holds remain open.", "No function registers events, changes legal status, issues certificates, transmits notifications or decides rights.", "Apply jurisdiction-specific lawful purpose and minimum disclosure; a subject does not control every register act or every co-participant record.", "Unregistered, disputed and incomplete evidence never authorizes denial of personhood; missing records do not prove a negative status." ], "crud": { "read": [ "Return authorized minimal views with jurisdiction, period, provenance and uncertainty." ], "create": [ "Require dossier namespace, subject reference or explicit unresolved subject, custodian and declared profile; permit pending evidence." ], "update": [ "Record local supported assertions and revision links; official master changes require their own authority and system." ], "delete": [ "Custodian-approved retention, legal holds and lawful disposal govern local copies. The adopting records service owns execution and evidence; retain only a lawful minimal non-identifying tombstone.", "No automatic deletion of authoritative civil entries or indefinite retention of protected historical payloads is implied." ] }, "roles": [ { "name": "Dossier custodian", "responsibilities": [ "Maintain accountable local scope and provenance" ] }, { "name": "Authorized registration liaison", "responsibilities": [ "Verify external register references without impersonating the registrar" ] }, { "name": "Qualified civil-status reviewer", "responsibilities": [ "Assess profile applicability, disputes and recognition evidence" ] }, { "name": "Access and records officer", "responsibilities": [ "Approve recipient views, retention and disposition" ] }, { "name": "Subject or authorized representative", "responsibilities": [ "Supply evidence and exercise permitted access or correction routes" ] } ], "access": { "default_rule": "Deny content access unless role, lawful purpose and record scope are established, including for a status-only answer.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Statutory or emergency disclosure needs explicit authority, minimal scope and a recorded responsible decision; no blanket bypass.", "Protected adoption, earlier-name or marker information requires a specialist profile; age of a record does not automatically open it." ], "audit_requirements": [ "Reference access and mutation audit evidence with minimal actor, purpose, scope, revision and result; apply a separate lawful retention rule." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "AGENTS.md and custodian authority/access policy", "spec.yaml and all research holds", "Pinned jurisdiction profile and authorized source evidence" ] } }, "coverage": { "claim": "Source-grounded proposed civil-status dossier structure with international registration concepts and selected European document and correction examples. Separate local no-tools self-audit completed. This noncanonical reviewable draft preserves source, independent-review, legal-profile and conformance holds; it does not establish universal legal effects.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Separate dossier, person, event, entry and issuance identities." }, { "dimension": "lifecycle", "status": "covered", "notes": "Pending reports, registered assertions, challenges, corrections and governed retirement." }, { "dimension": "relationships", "status": "covered", "notes": "Subject/participants and optional pinned neighbor references; no target lifecycle ownership." }, { "dimension": "temporal", "status": "covered", "notes": "Effective and recording times, partial precision and retrospective corrections." }, { "dimension": "provenance", "status": "covered", "notes": "Source attribution, evidence assessment and revision links." }, { "dimension": "ownership", "status": "covered", "notes": "Role-based custodian mandate and external registrar/issuer masters." }, { "dimension": "validation", "status": "gap", "notes": "Research schema validation does not validate civil records or legal status; typed profiles and fixtures remain pending." }, { "dimension": "access", "status": "covered", "notes": "Purpose-specific minimal views and protected-history restrictions." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Authoritative preservation differs from local copy disposition; qualified policy required." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual mappings and recognition evidence only; no tested adapters." }, { "dimension": "direct properties", "status": "covered", "notes": "Civil event category, place, time and status scope; physical measurements belong to external clinical records." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Distinguish occurrence, registration, certificate authenticity and legal recognition." }, { "dimension": "capabilities and hazards", "status": "covered", "notes": "Six proposed local operations with refusal rules; false status, identity collision and disclosure are hazards." }, { "dimension": "context and evidence", "status": "covered", "notes": "Profiles, authority, incomplete chains and contested assertions retained." } ], "known_omissions": [ "Independent external review is absent; the separate local self-audit is not a second provider.", "Direct HTTP checks were not attempted under the owner-reported sandbox restriction; source versions and full EUR-Lex texts remain unverified.", "No typed nested instance schema, implemented operation, legal rule engine or executable mapping is provided.", "Name/marker changes, adoption confidentiality, presumed death, displaced persons, conflict-of-laws cases and non-European operational profiles require specialist research.", "Medical event classification, nationality, capacity, family master records and benefit consequences remain externally governed." ], "conflicts": [], "regional_assumptions": [ "UN statistical definitions are conceptual evidence, not binding worldwide civil law.", "England and Wales correction guidance and EU document/privacy examples do not establish a Cyprus or global operating profile." ], "adversarial_checks": [ "Reject person existence or nonexistence inferred from registration absence.", "Reject latest upload or a complete-looking event chain as proof of legal status.", "Reject apostille authenticity as legal-effect recognition.", "Reject automatic disclosure, identity retirement or benefit changes from local events." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "aggregate", "status": "accepted", "rationale": "A subject/profile-scoped dossier groups separately identified event assertions, registrations, status evidence and certificates over time. The person, civil register and issuance masters remain external. This proposed aggregate resolves the event/state title without equating those objects; standalone-mm is only the registry record-plane classification." }, "decisions": [ { "concept": "Dossier aggregate boundary", "disposition": "accepted as proposed", "rationale": "The scope is one subject reference and declared jurisdiction/profile, with separate dossiers permitted. It groups local evidence and does not claim registry, person or certificate master identity." }, { "concept": "Subject resolution and custodianship", "disposition": "accepted", "rationale": "Opaque dossier identity, unresolved linkage, role evidence and duplicate review prevent name-based merging and distinguish participant interests from registrar and custodian authority." }, { "concept": "Civil existence at registration", "disposition": "rejected", "rationale": "The legacy and supplement overreach is excluded. Missing registration is representable and does not authorize modeling a person as nonexistent or an occurrence as disproved." }, { "concept": "Vital and union classifications", "disposition": "qualified", "rationale": "Questions retain category evidence, applicable profile and occurrence/effect separation. Statistical terminology does not become a medical determination or a universal capacity or civil-status rule." }, { "concept": "Civil changes and protected history", "disposition": "limited", "rationale": "Name and family-change references are supported at a conceptual level. Recorded marker changes and specialized adoption profiles remain deferred; earlier names and family links are not default disclosure fields." }, { "concept": "Registration and delayed intake", "disposition": "accepted", "rationale": "Pending or unregistered occurrences, uncertain entry references and profile-dependent delay assessments avoid a universal deadline and permit missing registration evidence." }, { "concept": "One-to-one registration identity", "disposition": "rejected", "rationale": "Multiple jurisdictional entries, transcriptions and unresolved alternatives remain possible. Event, entry and certificate identities are not collapsed by the legacy cardinality claim." }, { "concept": "Correction and local retention", "disposition": "qualified", "rationale": "Request, authorized outcome and local supersession are separated. A regional annotation example does not mandate indefinite historical payload retention in every dossier copy." }, { "concept": "Universal status derivation", "disposition": "rejected", "rationale": "A jurisdiction-qualified attestation may support a status assertion even when its complete event chain is unavailable. Evidence gaps are explicit and do not authorize a reconstructed legal history." }, { "concept": "Time and competing views", "disposition": "accepted", "rationale": "Effective intervals and recording instants remain separate. Backdated corrections and differing jurisdictional views do not make the latest uploaded record universally controlling." }, { "concept": "Certificate authenticity and recognition", "disposition": "separated", "rationale": "Issuance identity, copy provenance, recipient suitability, authentication formalities and legal-effect recognition have separate questions and evidence. Apostille or translation support cannot decide substantive status." }, { "concept": "Legacy registry and downstream relations", "disposition": "reconciled", "rationale": "Registry extension and mandatory event-log composition are rejected for this dossier root. Candidate external references confer no identity retirement, benefit determination or automatic notification authority." }, { "concept": "Proposed local functions and access", "disposition": "accepted with scope limits", "rationale": "All six operations are explicitly unimplemented and local, with refusal paths and role/revision checks. Status-only projections still need authorization and must retain material uncertainty." }, { "concept": "Source and executable coverage", "disposition": "held", "rationale": "Seven substantive browser documents and two indexed-only legal references support a bounded draft. No direct HTTP measurement, current-law certification, typed instance schema or tested runtime conformance is claimed." }, { "concept": "Independent external review", "disposition": "waived and held", "rationale": "Claude and Grok were explicitly skipped with zero attempts. This separate frozen-evidence Codex assessment is a local self-audit and cannot be described as independent provider agreement." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; the separate Codex no-tools self-audit is not a second-provider review.", "Live source and version verification is incomplete. Direct HTTP checks were not attempted under the owner-reported sandbox restriction; no HTTP status was measured. Seven sources had substantive browser content available, while the two EUR-Lex sources have selected indexed evidence only. The coordinator must run check_sources.py and complete claim/version review.", "Qualified jurisdiction and legal-profile review is required before operational use, including civil effects, recognition, protected history, registration delays, translations, licensing, privacy and retention. International recommendations and selected European examples are not a universal civil-status rule set.", "Typed nested instance schemas, pinned neighbor bindings, implemented operations, executable mappings and adversarial fixtures remain incomplete. No runtime, legal-compliance or source-currentness certification is claimed.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Complete live URL, authoritative text, version, jurisdiction applicability and claim-level verification for all admitted sources, especially the two indexed-only EUR-Lex references.", "Develop specialist profiles for recorded marker changes, protected adoption information, presumed death, displaced persons and competing legal jurisdictions.", "Implement and test typed profiles with missing registration, duplicate identity, delayed entry, disputed death, retrospective correction, sealed history and authentication-without-recognition fixtures.", "Restore independent external review before canonical or publishable-draft promotion." ] }, "statistics": { "sources": 9, "bundles": 7, "layers": 14, "findings": 14, "questions": 42, "artifacts": 14, "functions": 6 } }