{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-per-006","code":"wm-per-006-life-event-civil-status","url":"https://ver.cy/models/wm-per-006-life-event-civil-status/","name":"Life Event / Civil Status","alternateNames":["B12"],"kind":"world-model","status":"published","version":"0.3.0","language":"en","classifiers":{"family":"World Models","category":"Society, people and institutions","entryKind":"aggregate","plane":"","domain":["SOC.PER.CIV"],"industry":["Cross-industry"],"navPath":"NAV.SOC.PER.CIV","tags":["life","event","civil","status","soc.per.civ"],"facets":{}},"whatItIs":"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.","purpose":"Maintain an evidence-qualified civil-status dossier linking a subject to life events, registrations, status assertions and certifications.","scope":{"in":["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":["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"],"boundaries":[{"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."},{"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."},{"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."},{"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."},{"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."}]},"distinguishingFeatures":["Unlike WM-PER-001 Person: Subject and other participants remain separately mastered; unresolved subject linkage is allowed and does not erase an event or deny personhood.","Unlike WM-XCT-013 Registry Pattern and WM-XCT-016 Identity Register: The dossier references civil entries and identity anchors; it is not a registry specialization and does not create or retire identity masters.","Unlike WM-XCT-017 Attestation / Credential: Certificates retain issuer, issuance identity and scope separate from an event or entry; the dossier only indexes attestations.","Unlike WM-XCT-015 Event Register and WM-POL-012 Public Benefit / Program: Optional audit/notification and downstream review references do not mandate publication or grant benefit rights. Generic logs and decisions remain external.","Unlike Legacy B12 and unreviewed supplement: 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."],"structure":{"bundles":[{"id":"bundle-scope","name":"Dossier scope and stewardship","description":"Dossier identity and a declared profile bound every assertion.","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.","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.","questions":[{"text":"Which opaque dossier key and namespace identify this subject-scoped record?","id":"q-identity-1","kind":"identity"},{"text":"Which subject and participant references are resolved, provisional or disputed?","id":"q-identity-2","kind":"relationship"},{"text":"What evidence distinguishes a duplicate dossier from distinct people or events?","id":"q-identity-3","kind":"quality"}]}]},{"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.","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.","questions":[{"text":"Which event categories and civil-status dimensions does this jurisdiction profile cover?","id":"q-profile-1","kind":"classification"},{"text":"What mandate authorizes the custodian to maintain each local assertion?","id":"q-profile-2","kind":"authority"},{"text":"Which authority retains each register or certificate master and handles disputes?","id":"q-profile-3","kind":"ownership"}]}]}]},{"id":"bundle-occurrences","name":"Vital and union events","description":"Record occurrence evidence without conflating registration and legal effect.","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.","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.","questions":[{"text":"What birth or death occurrence is asserted and how is its event category supported?","id":"q-vital-1","kind":"event"},{"text":"Which occurrence place and time are known, approximate or disputed?","id":"q-vital-2","kind":"spatial"},{"text":"Which profile-specific evidence or category review remains unresolved for this occurrence?","id":"q-vital-3","kind":"constraint"}]}]},{"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.","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.","questions":[{"text":"Which union and participant references does this event concern?","id":"q-union-1","kind":"relationship"},{"text":"Which formation or termination category is asserted under the relevant profile?","id":"q-union-2","kind":"classification"},{"text":"Which occurrence and asserted effect dates apply to this union event?","id":"q-union-3","kind":"temporal"}]}]}]},{"id":"bundle-change-intake","name":"Civil changes and registration intake","description":"Changes and pending reports remain evidenced, scoped assertions.","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.","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.","questions":[{"text":"Which civil attribute or family-status assertion is being changed?","id":"q-changes-1","kind":"definition"},{"text":"What act or decision supports this civil change and its claimed scope?","id":"q-changes-2","kind":"evidence"},{"text":"Which earlier names or family links require a restricted or sealed reference?","id":"q-changes-3","kind":"privacy"}]}]},{"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.","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.","questions":[{"text":"Which report or notification supplied the event assertion?","id":"q-intake-1","kind":"process"},{"text":"What is the evidenced registration state and which evidence is still missing?","id":"q-intake-2","kind":"state"},{"text":"Which applicable rule and circumstances explain a late or delayed registration assessment?","id":"q-intake-3","kind":"exception"}]}]}]},{"id":"bundle-registration","name":"Registration continuity","description":"Entry linkage and corrections preserve authority and disagreement.","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.","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.","questions":[{"text":"Which register namespace and entry identifier anchor each registration claim?","id":"q-entry-1","kind":"identity"},{"text":"How was each entry reference obtained and assessed?","id":"q-entry-2","kind":"provenance"},{"text":"Which entries are originals, transcriptions or unresolved alternatives for this event?","id":"q-entry-3","kind":"composition"}]}]},{"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.","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.","questions":[{"text":"Which assertion or entry is challenged, corrected or superseded?","id":"q-correction-1","kind":"lifecycle"},{"text":"What authority and evidence support the recorded correction outcome?","id":"q-correction-2","kind":"authority"},{"text":"Which historical payload remains necessary or restricted after the correction?","id":"q-correction-3","kind":"retention"}]}]}]},{"id":"bundle-status","name":"Status and time","description":"Qualified status assertions retain temporal and jurisdictional context.","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.","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.","questions":[{"text":"Which civil-status value is asserted for this jurisdiction and reference period?","id":"q-status-1","kind":"state"},{"text":"Which attestation, decision or event evidence supports this status assertion?","id":"q-status-2","kind":"evidence"},{"text":"What assessment supports acceptance, qualification or dispute of this status view?","id":"q-status-3","kind":"decision"}]}]},{"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.","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.","questions":[{"text":"Which effective intervals and recording instants belong to each status version?","id":"q-timeline-1","kind":"temporal"},{"text":"Which overlaps or gaps prevent a consistent view for the requested date?","id":"q-timeline-2","kind":"validation"},{"text":"How does a retrospective correction affect an earlier projection without rewriting its provenance?","id":"q-timeline-3","kind":"exception"}]}]}]},{"id":"bundle-certification","name":"Certification and recognition","description":"Document identity, authenticity and civil effect are different assessments.","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.","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.","questions":[{"text":"Which issuer and issuance identifier distinguish this certificate from its source entry?","id":"q-certificate-1","kind":"identity"},{"text":"What provenance and authenticity assessment accompany the presented copy?","id":"q-certificate-2","kind":"evidence"},{"text":"What recipient purpose and profile determine whether this certificate is suitable now?","id":"q-certificate-3","kind":"requirement"}]}]},{"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.","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.","questions":[{"text":"Which origin and receiving jurisdictions and document rules govern this presentation?","id":"q-recognition-1","kind":"interoperability"},{"text":"What evidence supports authenticity or a formalities exemption for this document?","id":"q-recognition-2","kind":"validation"},{"text":"Which competent assessment addresses recognition of the claimed legal effects?","id":"q-recognition-3","kind":"authority"}]}]}]},{"id":"bundle-governance","name":"Disclosure and continuity","description":"Access, retention and downstream references are purpose-bound.","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.","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.","questions":[{"text":"Which recipient entitlement permits the requested status or event view?","id":"q-disclosure-1","kind":"access"},{"text":"Which fields and linked participants must be hidden in this projection?","id":"q-disclosure-2","kind":"security"},{"text":"Which mapping losses would make a status-only projection misleading?","id":"q-disclosure-3","kind":"interoperability"}]}]},{"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.","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.","questions":[{"text":"Which retention rule, legal hold or lawful disposal decision applies to each local copy?","id":"q-continuity-1","kind":"retention"},{"text":"Which authorized downstream references need review after an evidenced change?","id":"q-continuity-2","kind":"relationship"},{"text":"What evidence is required before this dossier profile can be used operationally?","id":"q-continuity-3","kind":"validation"}]}]}]}]},"agentConduct":{"may":["Resolve a qualified dossier reference: Proposed operation, not implemented. Return exact or unresolved subject-scoped references without merging people by name or date.","Record an evidenced event assertion: Proposed operation, not implemented. Append a local occurrence assertion while keeping registration and effect unknown unless evidenced.","Link a registration reference: Proposed operation, not implemented. Add an authority-qualified entry reference and its assessment without changing the register.","Record an existing status assessment: Proposed operation, not implemented. Capture an authorized attestation or assessment with its jurisdiction and period. Do not compute legal status from event order.","Link an authorized correction outcome: Proposed operation, not implemented. Record a correction or challenge reference and local supersession with restricted history.","Prepare an authorized dossier projection: 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."],"mustNot":["Unregistered, disputed and incomplete evidence never authorizes denial of personhood; missing records do not prove a negative status.","Deny content access unless role, lawful purpose and record scope are established, including for a status-only answer."],"requiresHuman":[]},"ethics":{"considerations":["England and Wales correction guidance and EU document/privacy examples do not establish a Cyprus or global operating profile."],"affectedParties":[]},"owners":{"steward":"Accountable dossier custodian role and evidenced mandate","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"]}],"masterSystems":[]},"relations":[{"target":"WM-PER-001","type":"references","note":"Candidate person binding; subjects and participants remain separately mastered, including provisional unresolved references."},{"target":"WM-XCT-013","type":"aligned","note":"Candidate registry concepts only; reject legacy EXTEND because the root is a dossier, not the civil register."},{"target":"WM-XCT-016","type":"references","note":"Candidate identity register reference; no automatic birth creation or death retirement of the identity master."},{"target":"WM-XCT-017","type":"references","note":"Candidate attestation binding; certificate issuance and credential lifecycle stay external."},{"target":"WM-XCT-015","type":"references","note":"Optional authorized audit or change-event reference; reject mandatory public log composition."},{"target":"WM-POL-012","type":"references","note":"Optional downstream program review reference; no eligibility or entitlement inference."},{"target":"UN CRVS Revision 3","type":"aligned","note":"Selected concepts only; statistical terminology is not a universal substantive civil law."},{"target":"PROV-O 2013","type":"aligned","note":"Conceptual assertion provenance mapping; no executable conformance claim."},{"target":"WM-PER-001 Person","type":"neighbor","note":"Subject and other participants remain separately mastered; unresolved subject linkage is allowed and does not erase an event or deny personhood."},{"target":"WM-XCT-013 Registry Pattern and WM-XCT-016 Identity Register","type":"neighbor","note":"The dossier references civil entries and identity anchors; it is not a registry specialization and does not create or retire identity masters."},{"target":"WM-XCT-017 Attestation / Credential","type":"neighbor","note":"Certificates retain issuer, issuance identity and scope separate from an event or entry; the dossier only indexes attestations."},{"target":"WM-XCT-015 Event Register and WM-POL-012 Public Benefit / Program","type":"neighbor","note":"Optional audit/notification and downstream review references do not mandate publication or grant benefit rights. Generic logs and decisions remain external."},{"target":"Legacy B12 and unreviewed supplement","type":"neighbor","note":"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."}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier with namespace and revision","Governed external URI with version and authority context","Locally assigned opaque UUID with reconciliation status"]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":[]},"capabilities":{"applicability":"required","items":["Resolve a qualified dossier reference: Proposed operation, not implemented. Return exact or unresolved subject-scoped references without merging people by name or date.","Record an evidenced event assertion: Proposed operation, not implemented. Append a local occurrence assertion while keeping registration and effect unknown unless evidenced.","Link a registration reference: Proposed operation, not implemented. Add an authority-qualified entry reference and its assessment without changing the register.","Record an existing status assessment: Proposed operation, not implemented. Capture an authorized attestation or assessment with its jurisdiction and period. Do not compute legal status from event order.","Link an authorized correction outcome: Proposed operation, not implemented. Record a correction or challenge reference and local supersession with restricted history.","Prepare an authorized dossier projection: 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."]},"hazards":{"applicability":"optional","items":[]},"interfaces":{"applicability":"required","items":["PROV-O: The PROV Ontology"]},"context":{"applicability":"required","items":["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."]}},"sources":[{"title":"Principles and Recommendations for a Vital Statistics System, Revision 3","url":"https://unstats.un.org/unsd/demographic/standmeth/principles/m19rev3en.pdf","note":"United Nations Statistics Division"},{"title":"Convention on the Rights of the Child","url":"https://www.unicef.org/child-rights-convention/convention-text","note":"United Nations Children's Fund"},{"title":"Convention Abolishing the Requirement of Legalisation for Foreign Public Documents","url":"https://www.hcch.net/en/instruments/conventions/full-text/?cid=41","note":"Hague Conference on Private International Law"},{"title":"Regulation (EU) 2016/1191","url":"https://eur-lex.europa.eu/eli/reg/2016/1191/oj/eng","note":"European Parliament and Council of the European Union"},{"title":"Public documents","url":"https://e-justice.europa.eu/topics/your-rights/public-documents_en","note":"European Commission"},{"title":"Correct a birth registration: What corrections can be made","url":"https://www.gov.uk/correct-birth-registration","note":"General Register Office"},{"title":"General Data Protection Regulation","url":"https://eur-lex.europa.eu/eli/reg/2016/679","note":"European Parliament and Council of the European Union"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"World Wide Web Consortium"},{"title":"Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/rfc/rfc3339","note":"Internet Engineering Task Force"}],"openQuestions":["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.","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."],"resources":{"spec":"/models/wm-per-006-life-event-civil-status/spec.yaml","agents":"/models/wm-per-006-life-event-civil-status/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-per-006"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-per-006-life-event-civil-status/spec.yaml"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-10-06T15:27:18Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"derived","structure":"filled","agentConduct":"derived","ethics":"derived","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"missing","interaction.capabilities":"filled","interaction.hazards":"missing","interaction.interfaces":"derived","interaction.context":"filled","sources":"filled"},"notes":{"distinguishingFeatures":"Derived from boundary notes against neighbouring models.","agentConduct":"Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.","ethics":"Sentences mentioning harm, privacy, consent or similar, collected from the specification.","interaction.properties":"Institutional or informational subject: no invented physical properties."},"score":0.75}}