# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T14:38:18Z", "synthesisSha256": "1832dc519406a3aed95f061ab423a865dc49b3b3985ba0a64add7a4c09be9ede", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ECO-003", "registryId": "vr.wm-eco-003", "name": "Insurance", "version": "0.3.0-research.1", "previousVersions": [ { "version": "0.2.0-legacy", "url": "https://github.com/ver-cy/world-models/blob/feat/mega-model-registry/models/economy/C8-insurance-and-risk-pooling.md" } ], "entryKind": "aggregate", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.ECO.INS" ], "tags": [ "insurance", "soc.eco.ins" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-eco-003-insurance/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-eco-003", "model": { "registry_id": "vr.wm-eco-003", "model_id": "WM-ECO-003", "name": "Insurance", "entry_kind": "aggregate", "purpose": "Describe one policy-centered insurance arrangement and its coverage, premium, risk-transfer, reporting and claim interfaces.", "scope_statement": "A proposed aggregate rooted in one policy arrangement, with local coverage and premium schedules and typed references to parties, pools, claims and reports. It supports an arrangement before any claim exists. It does not represent the entire insurer, the insurance market or a pool-only scheme. Legal validity and financial execution remain external.", "in_scope": [ "Stable policy arrangement identity and versioned coverage and premium components", "Party role bindings, underwriting and distribution evidence, effective-time continuity", "Policy-level pool and reinsurance allocations, financial-assurance references and claim/redress links", "Restricted projections, provenance, access and local retention context" ], "out_of_scope": [ "Claim master identity, claim lines and amendments; claim handling workflows; loss, decision, dispute and payment masters", "Insurer corporate governance, standalone pool administration, treaty formation, actuarial reserving and solvency computation", "Issuing binding cover, certifying coverage, rating risk, denying claims, paying funds or making legal decisions", "Complete life, health, annuity, parametric, mutual, public-scheme and cross-border profiles" ], "boundary_notes": [ { "neighbor": "WM-ECO-036", "distinction": "Preserve the registry CONTAINS candidate as optional contextual composition. Claim identity, request assertions, lines and amendments belong to the claim master; zero-to-many links, possible cross-policy association and no cascade. Cardinality remains a proposed profile rule.", "source_refs": [ "SRC-001", "SRC-007" ] }, { "neighbor": "WM-ACT-045", "distinction": "Insurance Claim Handling owns task execution and handling progress; only source-qualified summaries are referenced here.", "source_refs": [ "SRC-001" ] }, { "neighbor": "WM-ECO-006", "distinction": "Commercial Contract supplies generic agreement references. Legacy EXTEND is qualified to an optional semantic reference until inheritance is validated.", "source_refs": [ "SRC-002" ] }, { "neighbor": "WM-ECO-002", "distinction": "Price / Valuation supplies independent insured-interest valuation and appraisal evidence.", "source_refs": [ "SRC-002", "SRC-004" ] }, { "neighbor": "WM-ECO-009", "distinction": "Payment owns payment authorization, execution, reversal and settlement; local allocations never move funds.", "source_refs": [ "SRC-002", "SRC-007" ] }, { "neighbor": "WM-ORG-001", "distinction": "Organization owns legal-entity masters; insurer, pool operator and intermediary roles are local bindings.", "source_refs": [ "SRC-001" ] }, { "neighbor": "WM-PER-001", "distinction": "Person owns natural-person identity; insured, policyholder and beneficiary roles do not duplicate that master.", "source_refs": [ "SRC-006" ] }, { "neighbor": "WM-XCT-035", "distinction": "Retention / Disposition supplies rule and decision references; adopting storage service owns actual disposal execution.", "source_refs": [ "SRC-005" ] }, { "neighbor": "Pool and reinsurance treaty master", "distinction": "Pool governance, treaty lifecycle and portfolio membership stay externally mastered; only policy-level allocations and assurance links are local.", "source_refs": [ "SRC-001" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Insurance Core Principles and ComFrame", "organization": "International Association of Insurance Supervisors", "url": "https://www.iaisweb.org/uploads/2024/12/IAIS-ICPs-and-ComFrame-adopted-in-December-2024.pdf", "version_or_date": "December 2024 edition; selected ICPs 13, 14, 18, 19, 20 and 21", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:37:04Z", "relevance": "Supervisory context for risk transfer, conduct, claims interfaces and reporting. Selected sections reviewed; no universal legal rule or current consolidation claim." }, { "id": "SRC-002", "title": "IFRS 17 Insurance Contracts - official overview", "organization": "IFRS Foundation", "url": "https://www.ifrs.org/issued-standards/list-of-standards/ifrs-17-insurance-contracts/", "version_or_date": "Living overview accessed 2026-10-06; standard effective from 2023 as described on page", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:37:04Z", "relevance": "Insurance-risk classification and separate accounting groups, measurement and service results; overview only, not a licensed implementation of the standard." }, { "id": "SRC-003", "title": "Q&A 2525 - Signature requirements relating to demands and needs statement", "organization": "European Insurance and Occupational Pensions Authority", "url": "https://www.eiopa.europa.eu/qa-regulation/questions-and-answers-database/2525-signature-requirements-relating-demands-and-needs-statement_en", "version_or_date": "Final Q&A; submission 2022-11-16; accessed 2026-10-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:37:04Z", "relevance": "Customer needs, distribution responsibility and communication evidence; national insurance and civil law remain separate." }, { "id": "SRC-004", "title": "Solvency II - regulatory framework overview", "organization": "European Insurance and Occupational Pensions Authority", "url": "https://www.eiopa.europa.eu/browse/regulation-and-policy/solvency-ii_en", "version_or_date": "Living overview accessed 2026-10-06; distinguishes later rules taking effect in 2027", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:37:04Z", "relevance": "Separate valuation, capital, governance and reporting contexts. No quantitative solvency formula admitted." }, { "id": "SRC-005", "title": "Principle (e): Storage limitation", "organization": "Information Commissioner's Office", "url": "https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/data-protection-principles/a-guide-to-the-data-protection-principles/storage-limitation/", "version_or_date": "Living UK guidance accessed 2026-10-06; page flags review following legislative change", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:37:04Z", "relevance": "Purpose-specific retention and disposal; no universal insurance retention duration." }, { "id": "SRC-006", "title": "A guide to lawful basis", "organization": "Information Commissioner's Office", "url": "https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/lawful-basis/a-guide-to-lawful-basis/", "version_or_date": "Living UK guidance accessed 2026-10-06; jurisdiction and amendment review required", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:37:04Z", "relevance": "Processing purpose and lawful basis must be recorded; consent is not the sole possible basis. Sensitive-data conditions require separate review." }, { "id": "SRC-007", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation 2013-04-30", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:37:04Z", "relevance": "Entity, activity, agent and qualified derivation vocabulary for evidence provenance; attribution is not truth certification." }, { "id": "SRC-008", "title": "RFC 3339: Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "July 2002; sections 4 and 5.6", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:37:04Z", "relevance": "Timestamp representation with seconds and offsets; does not provide insurance deadline or coverage semantics." } ], "structure": { "bundles": [ { "id": "bundle-constitution", "name": "Identity and responsibility", "description": "Proposed insurance context for identity and responsibility.", "rationale": "Keep this concern explicit while preserving separately mastered records and profile-specific authority.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-007" ], "layers": [ { "id": "layer-identity", "name": "Policy identity context", "description": "A proposed aggregate keyed to one policy arrangement, including its coverage and premium schedules. The insurance business, pool and product definition are separate roots.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "findings": [ { "id": "finding-identity", "name": "Policy identity", "description": "A proposed aggregate keyed to one policy arrangement, including its coverage and premium schedules. The insurance business, pool and product definition are separate roots.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "questions": [ { "id": "finding-identity-q01", "text": "Which issuing namespace and master identifier identify this policy arrangement across amendments?", "kind": "identity", "answer_data": [ "finding-identity-data01", "issuer reference; policy identifier; predecessor and successor links; revision" ] }, { "id": "finding-identity-q02", "text": "Which insurance line, benefit basis and risk-transfer classification apply under the selected profile?", "kind": "classification", "answer_data": [ "finding-identity-data02", "line code and version; indemnity or benefit basis; classification rationale; unresolved classification" ] }, { "id": "finding-identity-q03", "text": "Which schedules belong to this policy and which records remain external references?", "kind": "composition", "answer_data": [ "finding-identity-data03", "coverage identifiers; premium schedule identifiers; claim links; pool and product references" ] } ], "data_elements": [ { "id": "finding-identity-data01", "name": "Identity context", "description": "Candidate field group: issuer reference; policy identifier; predecessor and successor links; revision. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "finding-identity-data02", "name": "Classification context", "description": "Candidate field group: line code and version; indemnity or benefit basis; classification rationale; unresolved classification. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "finding-identity-data03", "name": "Composition context", "description": "Candidate field group: coverage identifiers; premium schedule identifiers; claim links; pool and product references. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "artifacts": [ { "id": "finding-identity-artifact", "name": "Policy identity record", "description": "Proposed local evidence index or authorized projection; referenced master payloads remain separately governed.", "media_or_form": [ "Structured record", "Human-readable restricted view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace first; governed IRI next; otherwise adopting-Dimension UUID or ULID. Revisions and observed times are separate from identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-parties", "name": "Party roles and authority context", "description": "Proposed role bindings distinguish insurer, policyholder, insured, beneficiary and intermediary. Contract participation does not itself establish joint data ownership or full access.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "findings": [ { "id": "finding-parties", "name": "Party roles and authority", "description": "Proposed role bindings distinguish insurer, policyholder, insured, beneficiary and intermediary. Contract participation does not itself establish joint data ownership or full access.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "questions": [ { "id": "finding-parties-q01", "text": "Which parties occupy each role, and for what effective period?", "kind": "relationship", "answer_data": [ "finding-parties-data01", "party master references; role codes; beneficiary priority; valid interval" ] }, { "id": "finding-parties-q02", "text": "What evidence permits the recorded representative or intermediary to act for this arrangement?", "kind": "authority", "answer_data": [ "finding-parties-data02", "mandate reference; permitted acts; limits; issuer; expiry; verification status" ] }, { "id": "finding-parties-q03", "text": "Who stewards each local record and determines its permitted processing purposes?", "kind": "ownership", "answer_data": [ "finding-parties-data03", "steward roles; controller determination reference; responsibilities; disputed assignments" ] } ], "data_elements": [ { "id": "finding-parties-data01", "name": "Relationship context", "description": "Candidate field group: party master references; role codes; beneficiary priority; valid interval. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "finding-parties-data02", "name": "Authority context", "description": "Candidate field group: mandate reference; permitted acts; limits; issuer; expiry; verification status. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "finding-parties-data03", "name": "Ownership context", "description": "Candidate field group: steward roles; controller determination reference; responsibilities; disputed assignments. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "finding-parties-artifact", "name": "Party roles and authority record", "description": "Proposed local evidence index or authorized projection; referenced master payloads remain separately governed.", "media_or_form": [ "Structured record", "Human-readable restricted view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace first; governed IRI next; otherwise adopting-Dimension UUID or ULID. Revisions and observed times are separate from identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-coverage", "name": "Coverage and time", "description": "Proposed insurance context for coverage and time.", "rationale": "Keep this concern explicit while preserving separately mastered records and profile-specific authority.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "layers": [ { "id": "layer-terms", "name": "Coverage schedule context", "description": "Proposed coverage components bind interests to versioned terms, limits, deductibles and benefit triggers. They allow benefit-based products as well as indemnity without asserting legal coverage.", "source_refs": [ "SRC-001", "SRC-002" ], "findings": [ { "id": "finding-terms", "name": "Coverage schedule", "description": "Proposed coverage components bind interests to versioned terms, limits, deductibles and benefit triggers. They allow benefit-based products as well as indemnity without asserting legal coverage.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "finding-terms-q01", "text": "What interest, event or benefit trigger does each coverage component describe?", "kind": "definition", "answer_data": [ "finding-terms-data01", "interest reference; trigger wording; benefit type; wording revision" ] }, { "id": "finding-terms-q02", "text": "Which limits, deductibles, exclusions and conditions apply to that component?", "kind": "constraint", "answer_data": [ "finding-terms-data02", "amount and currency; limit basis; deductible basis; exclusion references; precedence rule" ] }, { "id": "finding-terms-q03", "text": "Which territories and governing-law profiles qualify the coverage?", "kind": "spatial", "answer_data": [ "finding-terms-data03", "risk location references; territorial scope; governing law reference; unresolved cross-border issue" ] } ], "data_elements": [ { "id": "finding-terms-data01", "name": "Definition context", "description": "Candidate field group: interest reference; trigger wording; benefit type; wording revision. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "finding-terms-data02", "name": "Constraint context", "description": "Candidate field group: amount and currency; limit basis; deductible basis; exclusion references; precedence rule. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "finding-terms-data03", "name": "Spatial context", "description": "Candidate field group: risk location references; territorial scope; governing law reference; unresolved cross-border issue. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "finding-terms-artifact", "name": "Coverage schedule record", "description": "Proposed local evidence index or authorized projection; referenced master payloads remain separately governed.", "media_or_form": [ "Structured record", "Human-readable restricted view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace first; governed IRI next; otherwise adopting-Dimension UUID or ULID. Revisions and observed times are separate from identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-continuity", "name": "Coverage continuity and amendments context", "description": "Proposed effective-time history separates issuance, inception, amendment, renewal, cancellation and runoff. A local record update cannot create legal effect.", "source_refs": [ "SRC-001", "SRC-008" ], "findings": [ { "id": "finding-continuity", "name": "Coverage continuity and amendments", "description": "Proposed effective-time history separates issuance, inception, amendment, renewal, cancellation and runoff. A local record update cannot create legal effect.", "source_refs": [ "SRC-001", "SRC-008" ], "questions": [ { "id": "finding-continuity-q01", "text": "Which effective interval and trigger dates govern this version of cover?", "kind": "temporal", "answer_data": [ "finding-continuity-data01", "inception; expiry; occurrence or claims-made basis; retroactive date; reporting extension; time zone" ] }, { "id": "finding-continuity-q02", "text": "What authorized evidence supports a renewal, cancellation, lapse or reinstatement?", "kind": "lifecycle", "answer_data": [ "finding-continuity-data02", "transition type; authority; notice evidence; disputed effect; predecessor revision" ] }, { "id": "finding-continuity-q03", "text": "How are late notification, backdated correction and unresolved gaps represented?", "kind": "exception", "answer_data": [ "finding-continuity-data03", "exception basis; observation time; effective time; disputed interval; reviewer status" ] } ], "data_elements": [ { "id": "finding-continuity-data01", "name": "Temporal context", "description": "Candidate field group: inception; expiry; occurrence or claims-made basis; retroactive date; reporting extension; time zone. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "finding-continuity-data02", "name": "Lifecycle context", "description": "Candidate field group: transition type; authority; notice evidence; disputed effect; predecessor revision. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "finding-continuity-data03", "name": "Exception context", "description": "Candidate field group: exception basis; observation time; effective time; disputed interval; reviewer status. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] } ], "artifacts": [ { "id": "finding-continuity-artifact", "name": "Coverage continuity and amendments record", "description": "Proposed local evidence index or authorized projection; referenced master payloads remain separately governed.", "media_or_form": [ "Structured record", "Human-readable restricted view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace first; governed IRI next; otherwise adopting-Dimension UUID or ULID. Revisions and observed times are separate from identity.", "source_refs": [ "SRC-001", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-placement", "name": "Placement and underwriting", "description": "Proposed insurance context for placement and underwriting.", "rationale": "Keep this concern explicit while preserving separately mastered records and profile-specific authority.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007" ], "layers": [ { "id": "layer-underwriting", "name": "Underwriting evidence context", "description": "A proposed record of the underwriting position and its inputs. It preserves uncertainty, restricted factors and authority without operating a rating or acceptance engine.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-underwriting", "name": "Underwriting evidence", "description": "A proposed record of the underwriting position and its inputs. It preserves uncertainty, restricted factors and authority without operating a rating or acceptance engine.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ], "questions": [ { "id": "finding-underwriting-q01", "text": "Which disclosures and observations informed the recorded underwriting position?", "kind": "evidence", "answer_data": [ "finding-underwriting-data01", "input references; originator; observation date; missing information; confidence" ] }, { "id": "finding-underwriting-q02", "text": "Which authorized assessment records the accepted, declined or referred position?", "kind": "decision", "answer_data": [ "finding-underwriting-data02", "assessment reference; decision author; rationale; conditions; pending review" ] }, { "id": "finding-underwriting-q03", "text": "Which proposed rating inputs require restriction or specialist review under the adopting profile?", "kind": "privacy", "answer_data": [ "finding-underwriting-data03", "factor categories; processing basis; sensitivity; prohibited-use policy; review outcome" ] } ], "data_elements": [ { "id": "finding-underwriting-data01", "name": "Evidence context", "description": "Candidate field group: input references; originator; observation date; missing information; confidence. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] }, { "id": "finding-underwriting-data02", "name": "Decision context", "description": "Candidate field group: assessment reference; decision author; rationale; conditions; pending review. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] }, { "id": "finding-underwriting-data03", "name": "Privacy context", "description": "Candidate field group: factor categories; processing basis; sensitivity; prohibited-use policy; review outcome. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "finding-underwriting-artifact", "name": "Underwriting evidence record", "description": "Proposed local evidence index or authorized projection; referenced master payloads remain separately governed.", "media_or_form": [ "Structured record", "Human-readable restricted view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace first; governed IRI next; otherwise adopting-Dimension UUID or ULID. Revisions and observed times are separate from identity.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-distribution", "name": "Needs and disclosure evidence context", "description": "Proposed placement evidence links customer needs, product disclosure and distribution responsibility. A signature is not a substitute for the assessment or a universal requirement.", "source_refs": [ "SRC-001", "SRC-003" ], "findings": [ { "id": "finding-distribution", "name": "Needs and disclosure evidence", "description": "Proposed placement evidence links customer needs, product disclosure and distribution responsibility. A signature is not a substitute for the assessment or a universal requirement.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "finding-distribution-q01", "text": "Which customer needs and product-profile requirements were recorded before placement?", "kind": "requirement", "answer_data": [ "finding-distribution-data01", "needs reference; product version; mismatch; advice status" ] }, { "id": "finding-distribution-q02", "text": "What disclosure version and communication channel were used for the recipient?", "kind": "process", "answer_data": [ "finding-distribution-data02", "document reference; language; accessibility; channel; delivery evidence" ] }, { "id": "finding-distribution-q03", "text": "Which unresolved mismatch, conflict of interest or missing disclosure requires review?", "kind": "quality", "answer_data": [ "finding-distribution-data03", "issue reference; responsible role; impact; review status; remediation reference" ] } ], "data_elements": [ { "id": "finding-distribution-data01", "name": "Requirement context", "description": "Candidate field group: needs reference; product version; mismatch; advice status. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "finding-distribution-data02", "name": "Process context", "description": "Candidate field group: document reference; language; accessibility; channel; delivery evidence. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "finding-distribution-data03", "name": "Quality context", "description": "Candidate field group: issue reference; responsible role; impact; review status; remediation reference. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "finding-distribution-artifact", "name": "Needs and disclosure evidence record", "description": "Proposed local evidence index or authorized projection; referenced master payloads remain separately governed.", "media_or_form": [ "Structured record", "Human-readable restricted view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace first; governed IRI next; otherwise adopting-Dimension UUID or ULID. Revisions and observed times are separate from identity.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-funding", "name": "Premium and risk transfer", "description": "Proposed insurance context for premium and risk transfer.", "rationale": "Keep this concern explicit while preserving separately mastered records and profile-specific authority.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "layers": [ { "id": "layer-premium", "name": "Premium obligations and receipts context", "description": "Proposed premium schedule and payment references retain distinct due, billed, collected, reversed and refunded values. Receipt alone does not prove coverage or accounting revenue.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "findings": [ { "id": "finding-premium", "name": "Premium obligations and receipts", "description": "Proposed premium schedule and payment references retain distinct due, billed, collected, reversed and refunded values. Receipt alone does not prove coverage or accounting revenue.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "questions": [ { "id": "finding-premium-q01", "text": "What premium amounts, currencies, taxes and fees are recorded for each installment?", "kind": "measurement", "answer_data": [ "finding-premium-data01", "decimal amount; currency code version; tax and fee components; calculation evidence" ] }, { "id": "finding-premium-q02", "text": "Which external receipts, reversals or refunds reconcile with each obligation?", "kind": "state", "answer_data": [ "finding-premium-data02", "payment master reference; allocation amount; reconciliation state; outstanding difference" ] }, { "id": "finding-premium-q03", "text": "What policy-qualified consequence is asserted for nonpayment or disputed collection?", "kind": "exception", "answer_data": [ "finding-premium-data03", "notice reference; grace condition; disputed balance; authorized coverage-effect determination" ] } ], "data_elements": [ { "id": "finding-premium-data01", "name": "Measurement context", "description": "Candidate field group: decimal amount; currency code version; tax and fee components; calculation evidence. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "finding-premium-data02", "name": "State context", "description": "Candidate field group: payment master reference; allocation amount; reconciliation state; outstanding difference. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "finding-premium-data03", "name": "Exception context", "description": "Candidate field group: notice reference; grace condition; disputed balance; authorized coverage-effect determination. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "artifacts": [ { "id": "finding-premium-artifact", "name": "Premium obligations and receipts record", "description": "Proposed local evidence index or authorized projection; referenced master payloads remain separately governed.", "media_or_form": [ "Structured record", "Human-readable restricted view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace first; governed IRI next; otherwise adopting-Dimension UUID or ULID. Revisions and observed times are separate from identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-cession", "name": "Pool participation and reinsurance links context", "description": "Proposed policy-level allocation references distinguish participation in a pool from reinsurance held. Economic risk transfer does not automatically replace the original obligor.", "source_refs": [ "SRC-001", "SRC-002" ], "findings": [ { "id": "finding-cession", "name": "Pool participation and reinsurance links", "description": "Proposed policy-level allocation references distinguish participation in a pool from reinsurance held. Economic risk transfer does not automatically replace the original obligor.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "finding-cession-q01", "text": "Which pool participation or treaty references attach to this exposure?", "kind": "relationship", "answer_data": [ "finding-cession-data01", "pool or treaty master; cedent; counterparty; allocation scope; effective period" ] }, { "id": "finding-cession-q02", "text": "Which share, attachment, limit and exclusion terms qualify the allocation?", "kind": "constraint", "answer_data": [ "finding-cession-data02", "share basis; attachment value; limit currency; treaty revision; missing terms" ] }, { "id": "finding-cession-q03", "text": "Which counterparty, basis or recovery uncertainty is recorded without assuming payment?", "kind": "quality", "answer_data": [ "finding-cession-data03", "counterparty assessment reference; recoverable estimate reference; dispute; concentration concern" ] } ], "data_elements": [ { "id": "finding-cession-data01", "name": "Relationship context", "description": "Candidate field group: pool or treaty master; cedent; counterparty; allocation scope; effective period. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "finding-cession-data02", "name": "Constraint context", "description": "Candidate field group: share basis; attachment value; limit currency; treaty revision; missing terms. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "finding-cession-data03", "name": "Quality context", "description": "Candidate field group: counterparty assessment reference; recoverable estimate reference; dispute; concentration concern. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "finding-cession-artifact", "name": "Pool participation and reinsurance links record", "description": "Proposed local evidence index or authorized projection; referenced master payloads remain separately governed.", "media_or_form": [ "Structured record", "Human-readable restricted view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace first; governed IRI next; otherwise adopting-Dimension UUID or ULID. Revisions and observed times are separate from identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-assurance", "name": "Reporting and financial assurance", "description": "Proposed insurance context for reporting and financial assurance.", "rationale": "Keep this concern explicit while preserving separately mastered records and profile-specific authority.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "layers": [ { "id": "layer-valuation", "name": "Valuation and accounting references context", "description": "Proposed reporting links keep policy amounts distinct from accounting groups and prudential measures. Calculations and ledger posting remain external.", "source_refs": [ "SRC-002", "SRC-004" ], "findings": [ { "id": "finding-valuation", "name": "Valuation and accounting references", "description": "Proposed reporting links keep policy amounts distinct from accounting groups and prudential measures. Calculations and ledger posting remain external.", "source_refs": [ "SRC-002", "SRC-004" ], "questions": [ { "id": "finding-valuation-q01", "text": "Which measurement purpose, accounting group and adopted standard version apply to the referenced report?", "kind": "classification", "answer_data": [ "finding-valuation-data01", "report purpose; group reference; measurement basis; standard version; jurisdiction" ] }, { "id": "finding-valuation-q02", "text": "Which amounts are gross, ceded or net, and what period and currency qualify them?", "kind": "measurement", "answer_data": [ "finding-valuation-data02", "amount type; currency; valuation date; gross or ceded basis; uncertainty; report reference" ] }, { "id": "finding-valuation-q03", "text": "What reconciliation explains differences between policy, claim and reporting figures?", "kind": "validation", "answer_data": [ "finding-valuation-data03", "reconciliation reference; population boundary; timing difference; unresolved discrepancy" ] } ], "data_elements": [ { "id": "finding-valuation-data01", "name": "Classification context", "description": "Candidate field group: report purpose; group reference; measurement basis; standard version; jurisdiction. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-004" ] }, { "id": "finding-valuation-data02", "name": "Measurement context", "description": "Candidate field group: amount type; currency; valuation date; gross or ceded basis; uncertainty; report reference. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-004" ] }, { "id": "finding-valuation-data03", "name": "Validation context", "description": "Candidate field group: reconciliation reference; population boundary; timing difference; unresolved discrepancy. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-004" ] } ], "artifacts": [ { "id": "finding-valuation-artifact", "name": "Valuation and accounting references record", "description": "Proposed local evidence index or authorized projection; referenced master payloads remain separately governed.", "media_or_form": [ "Structured record", "Human-readable restricted view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace first; governed IRI next; otherwise adopting-Dimension UUID or ULID. Revisions and observed times are separate from identity.", "source_refs": [ "SRC-002", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-solvency", "name": "Prudential assurance references context", "description": "Proposed links to external insurer or pool assurance reports. A policy-level link neither calculates capital adequacy nor guarantees future claim payment.", "source_refs": [ "SRC-001", "SRC-004" ], "findings": [ { "id": "finding-solvency", "name": "Prudential assurance references", "description": "Proposed links to external insurer or pool assurance reports. A policy-level link neither calculates capital adequacy nor guarantees future claim payment.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "finding-solvency-q01", "text": "Which insurer or pool report supports the stated financial-assurance context?", "kind": "evidence", "answer_data": [ "finding-solvency-data01", "report reference; reporting entity; scope; period; publication status" ] }, { "id": "finding-solvency-q02", "text": "Which applicable and future-effective regulatory versions qualify this report?", "kind": "temporal", "answer_data": [ "finding-solvency-data02", "regime reference; effective date; transition rule; current applicability review" ] }, { "id": "finding-solvency-q03", "text": "Which limitations prevent using the report as a policy-level guarantee?", "kind": "quality", "answer_data": [ "finding-solvency-data03", "scope mismatch; stale data; unverified assurance; insolvency or runoff reference; caveat" ] } ], "data_elements": [ { "id": "finding-solvency-data01", "name": "Evidence context", "description": "Candidate field group: report reference; reporting entity; scope; period; publication status. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "finding-solvency-data02", "name": "Temporal context", "description": "Candidate field group: regime reference; effective date; transition rule; current applicability review. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "finding-solvency-data03", "name": "Quality context", "description": "Candidate field group: scope mismatch; stale data; unverified assurance; insolvency or runoff reference; caveat. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "finding-solvency-artifact", "name": "Prudential assurance references record", "description": "Proposed local evidence index or authorized projection; referenced master payloads remain separately governed.", "media_or_form": [ "Structured record", "Human-readable restricted view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace first; governed IRI next; otherwise adopting-Dimension UUID or ULID. Revisions and observed times are separate from identity.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-claims", "name": "Claim and redress interfaces", "description": "Proposed insurance context for claim and redress interfaces.", "rationale": "Keep this concern explicit while preserving separately mastered records and profile-specific authority.", "source_refs": [ "SRC-001", "SRC-007" ], "layers": [ { "id": "layer-claim-links", "name": "Claim association context", "description": "Proposed contextual association with independently mastered claims. The registry containment candidate does not imply exclusive parentage, mandatory claims or deletion cascade.", "source_refs": [ "SRC-001", "SRC-007" ], "findings": [ { "id": "finding-claim-links", "name": "Claim association", "description": "Proposed contextual association with independently mastered claims. The registry containment candidate does not imply exclusive parentage, mandatory claims or deletion cascade.", "source_refs": [ "SRC-001", "SRC-007" ], "questions": [ { "id": "finding-claim-links-q01", "text": "Which independently identified claims invoke this policy and coverage revision?", "kind": "composition", "answer_data": [ "finding-claim-links-data01", "WM-ECO-036 claim references; coverage reference; link basis; disputed association" ] }, { "id": "finding-claim-links-q02", "text": "Which claim-side assertions and insurer positions are available without collapsing their states?", "kind": "state", "answer_data": [ "finding-claim-links-data02", "asserted status; source role; assessment or decision reference; observation time" ] }, { "id": "finding-claim-links-q03", "text": "How are multiple policies, multiple claimants and duplicate notifications linked without merging masters?", "kind": "constraint", "answer_data": [ "finding-claim-links-data03", "cross-policy links; claimant references; duplicate candidate; match evidence; resolution authority" ] } ], "data_elements": [ { "id": "finding-claim-links-data01", "name": "Composition context", "description": "Candidate field group: WM-ECO-036 claim references; coverage reference; link basis; disputed association. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "finding-claim-links-data02", "name": "State context", "description": "Candidate field group: asserted status; source role; assessment or decision reference; observation time. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "finding-claim-links-data03", "name": "Constraint context", "description": "Candidate field group: cross-policy links; claimant references; duplicate candidate; match evidence; resolution authority. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] } ], "artifacts": [ { "id": "finding-claim-links-artifact", "name": "Claim association record", "description": "Proposed local evidence index or authorized projection; referenced master payloads remain separately governed.", "media_or_form": [ "Structured record", "Human-readable restricted view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace first; governed IRI next; otherwise adopting-Dimension UUID or ULID. Revisions and observed times are separate from identity.", "source_refs": [ "SRC-001", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-outcomes", "name": "Outcome and complaint references context", "description": "Proposed summary links separate decision, agreement, settlement, payment, recovery and complaint. Handling workflows and legal redress are delegated.", "source_refs": [ "SRC-001", "SRC-007" ], "findings": [ { "id": "finding-outcomes", "name": "Outcome and complaint references", "description": "Proposed summary links separate decision, agreement, settlement, payment, recovery and complaint. Handling workflows and legal redress are delegated.", "source_refs": [ "SRC-001", "SRC-007" ], "questions": [ { "id": "finding-outcomes-q01", "text": "Which decision, settlement, payment or recovery records support the outcome summary?", "kind": "relationship", "answer_data": [ "finding-outcomes-data01", "typed master links; allowed amount reference; paid amount reference; unresolved recovery" ] }, { "id": "finding-outcomes-q02", "text": "What subsequent correction, reopening or partial outcome changes the available summary?", "kind": "event", "answer_data": [ "finding-outcomes-data02", "event reference; prior summary; effective time; observation time; source authority" ] }, { "id": "finding-outcomes-q03", "text": "Which reason and complaint-route information may each recipient receive?", "kind": "access", "answer_data": [ "finding-outcomes-data03", "reason document; recipient role; restricted fields; redress route reference; disclosure basis" ] } ], "data_elements": [ { "id": "finding-outcomes-data01", "name": "Relationship context", "description": "Candidate field group: typed master links; allowed amount reference; paid amount reference; unresolved recovery. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "finding-outcomes-data02", "name": "Event context", "description": "Candidate field group: event reference; prior summary; effective time; observation time; source authority. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "finding-outcomes-data03", "name": "Access context", "description": "Candidate field group: reason document; recipient role; restricted fields; redress route reference; disclosure basis. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] } ], "artifacts": [ { "id": "finding-outcomes-artifact", "name": "Outcome and complaint references record", "description": "Proposed local evidence index or authorized projection; referenced master payloads remain separately governed.", "media_or_form": [ "Structured record", "Human-readable restricted view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace first; governed IRI next; otherwise adopting-Dimension UUID or ULID. Revisions and observed times are separate from identity.", "source_refs": [ "SRC-001", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-records", "name": "Records and exchange", "description": "Proposed insurance context for records and exchange.", "rationale": "Keep this concern explicit while preserving separately mastered records and profile-specific authority.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-governance", "name": "Access and retention context context", "description": "Proposed record-specific access and disposition bindings. Views are purpose-limited; history must coexist with lawful payload deletion and unresolved preservation duties.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-governance", "name": "Access and retention context", "description": "Proposed record-specific access and disposition bindings. Views are purpose-limited; history must coexist with lawful payload deletion and unresolved preservation duties.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "finding-governance-q01", "text": "Which purpose and role authorize access to each underwriting, policy or linked-claim view?", "kind": "security", "answer_data": [ "finding-governance-data01", "purpose; role; authority reference; field restrictions; access decision evidence" ] }, { "id": "finding-governance-q02", "text": "Which retention trigger, review date and scoped hold apply to the local record?", "kind": "retention", "answer_data": [ "finding-governance-data02", "schedule reference; trigger event; hold scope; review date; disposition authority" ] }, { "id": "finding-governance-q03", "text": "What evidence resolves a conflict between correction, erasure and preservation duties?", "kind": "exception", "answer_data": [ "finding-governance-data03", "rights request reference; legal review; segregated payload; minimal tombstone; decision evidence" ] } ], "data_elements": [ { "id": "finding-governance-data01", "name": "Security context", "description": "Candidate field group: purpose; role; authority reference; field restrictions; access decision evidence. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "finding-governance-data02", "name": "Retention context", "description": "Candidate field group: schedule reference; trigger event; hold scope; review date; disposition authority. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "finding-governance-data03", "name": "Exception context", "description": "Candidate field group: rights request reference; legal review; segregated payload; minimal tombstone; decision evidence. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "finding-governance-artifact", "name": "Access and retention context record", "description": "Proposed local evidence index or authorized projection; referenced master payloads remain separately governed.", "media_or_form": [ "Structured record", "Human-readable restricted view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace first; governed IRI next; otherwise adopting-Dimension UUID or ULID. Revisions and observed times are separate from identity.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-interchange", "name": "Provenance and exchange profile context", "description": "Proposed exchange manifest preserves identity, derivation and time while stating mapping loss. Transport success, a hash or a vocabulary term is not substantive verification.", "source_refs": [ "SRC-007", "SRC-008" ], "findings": [ { "id": "finding-interchange", "name": "Provenance and exchange profile", "description": "Proposed exchange manifest preserves identity, derivation and time while stating mapping loss. Transport success, a hash or a vocabulary term is not substantive verification.", "source_refs": [ "SRC-007", "SRC-008" ], "questions": [ { "id": "finding-interchange-q01", "text": "Which master revision, source actor and transformation produced this projection?", "kind": "provenance", "answer_data": [ "finding-interchange-data01", "master reference; revision; activity reference; responsible role; transformation identifier" ] }, { "id": "finding-interchange-q02", "text": "Which exact exchange profile and licensed schema version are bound, and what information is lost?", "kind": "interoperability", "answer_data": [ "finding-interchange-data02", "profile identifier; schema version; license evidence; mapping; loss report; conformance status" ] }, { "id": "finding-interchange-q03", "text": "Which checks reject an export with unresolved references, ambiguous time or excessive disclosure?", "kind": "validation", "answer_data": [ "finding-interchange-data03", "reference check; timestamp check; authorization check; unresolved fields; refusal reasons" ] } ], "data_elements": [ { "id": "finding-interchange-data01", "name": "Provenance context", "description": "Candidate field group: master reference; revision; activity reference; responsible role; transformation identifier. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007", "SRC-008" ] }, { "id": "finding-interchange-data02", "name": "Interoperability context", "description": "Candidate field group: profile identifier; schema version; license evidence; mapping; loss report; conformance status. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007", "SRC-008" ] }, { "id": "finding-interchange-data03", "name": "Validation context", "description": "Candidate field group: reference check; timestamp check; authorization check; unresolved fields; refusal reasons. Nested schema and code bindings require profile validation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "finding-interchange-artifact", "name": "Provenance and exchange profile record", "description": "Proposed local evidence index or authorized projection; referenced master payloads remain separately governed.", "media_or_form": [ "Structured record", "Human-readable restricted view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace first; governed IRI next; otherwise adopting-Dimension UUID or ULID. Revisions and observed times are separate from identity.", "source_refs": [ "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "fn-register-arrangement", "name": "Register local arrangement", "description": "Proposed local operation to link an authorized policy master and define the aggregate boundary. Not implemented by this research package.", "inputs": [ "Master policy reference and namespace", "Profile and permitted steward" ], "outputs": [ "Local arrangement reference or refusal" ], "preconditions": [ "Authenticated authorized local role, allowed purpose and resolved source references", "Pinned profile, expected revision and concurrency check; refuse stale, ambiguous or unauthorized input" ], "effects": [ "Creates a local index only; does not issue or bind cover." ], "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "fn-record-coverage-revision", "name": "Record coverage revision", "description": "Proposed local operation to record source-qualified wording and effective intervals. Not implemented by this research package.", "inputs": [ "Prior revision", "Authorized amendment evidence", "Effective interval and observation time" ], "outputs": [ "New local revision or conflict report" ], "preconditions": [ "Authenticated authorized local role, allowed purpose and resolved source references", "Pinned profile, expected revision and concurrency check; refuse stale, ambiguous or unauthorized input" ], "effects": [ "Preserves prior interpretation and disputed periods; no legal amendment is executed." ], "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "fn-attach-placement-evidence", "name": "Attach placement evidence", "description": "Proposed local operation to associate underwriting and needs/disclosure evidence. Not implemented by this research package.", "inputs": [ "Assessment references", "Recipient-specific disclosure evidence", "Purpose authorization" ], "outputs": [ "Evidence links or refusal reasons" ], "preconditions": [ "Authenticated authorized local role, allowed purpose and resolved source references", "Pinned profile, expected revision and concurrency check; refuse stale, ambiguous or unauthorized input" ], "effects": [ "Adds attribution and gaps; does not assess suitability or set a premium." ], "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "fn-reconcile-premium-links", "name": "Reconcile premium references", "description": "Proposed local operation to compare supplied schedule and payment allocations. Not implemented by this research package.", "inputs": [ "Schedule revision", "Payment references", "Currency-qualified allocations" ], "outputs": [ "Reconciliation draft and unresolved differences" ], "preconditions": [ "Authenticated authorized local role, allowed purpose and resolved source references", "Pinned profile, expected revision and concurrency check; refuse stale, ambiguous or unauthorized input" ], "effects": [ "Records differences only; does not collect premiums, post ledgers or infer lapse." ], "source_refs": [ "SRC-002", "SRC-007" ] }, { "id": "fn-link-transfer-and-report", "name": "Link risk transfer and assurance", "description": "Proposed local operation to bind policy-level allocation and external report references. Not implemented by this research package.", "inputs": [ "Treaty or pool references", "Allocation terms", "Report purpose and period" ], "outputs": [ "Typed reference set or scope mismatch" ], "preconditions": [ "Authenticated authorized local role, allowed purpose and resolved source references", "Pinned profile, expected revision and concurrency check; refuse stale, ambiguous or unauthorized input" ], "effects": [ "Records provenance; does not cede risk, calculate reserves or certify solvency." ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "fn-link-claim-outcomes", "name": "Link claim and outcome records", "description": "Proposed local operation to maintain claim context with separately sourced outcome states. Not implemented by this research package.", "inputs": [ "Claim master links", "Coverage revision", "Authorized decision or payment references" ], "outputs": [ "Context links and stale-summary flags" ], "preconditions": [ "Authenticated authorized local role, allowed purpose and resolved source references", "Pinned profile, expected revision and concurrency check; refuse stale, ambiguous or unauthorized input" ], "effects": [ "No claim creation, handling, denial, settlement or payment is performed." ], "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "fn-prepare-restricted-view", "name": "Prepare restricted projection", "description": "Proposed local operation to compose a purpose-limited view for local review. Not implemented by this research package.", "inputs": [ "Recipient and purpose", "Access decision reference", "Selected revision and mapping profile" ], "outputs": [ "Local draft view and loss manifest or refusal" ], "preconditions": [ "Authenticated authorized local role, allowed purpose and resolved source references", "Pinned profile, expected revision and concurrency check; refuse stale, ambiguous or unauthorized input" ], "effects": [ "Does not send data, issue proof of cover or override payload retention controls." ], "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008" ] } ], "composition": [ { "target": "WM-ECO-036", "relation": "COMPOSE", "purpose": "Preserve the registry CONTAINS candidate as optional contextual composition. Claim identity, request assertions, lines and amendments belong to the claim master; zero-to-many links, possible cross-policy association and no cascade. Cardinality remains a proposed profile rule.", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "target": "WM-ACT-045", "relation": "REFERENCE", "purpose": "Insurance Claim Handling owns task execution and handling progress; only source-qualified summaries are referenced here.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "WM-ECO-006", "relation": "REFERENCE", "purpose": "Commercial Contract supplies generic agreement references. Legacy EXTEND is qualified to an optional semantic reference until inheritance is validated.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "WM-ECO-002", "relation": "REFERENCE", "purpose": "Price / Valuation supplies independent insured-interest valuation and appraisal evidence.", "required": false, "source_refs": [ "SRC-002", "SRC-004" ] }, { "target": "WM-ECO-009", "relation": "REFERENCE", "purpose": "Payment owns payment authorization, execution, reversal and settlement; local allocations never move funds.", "required": false, "source_refs": [ "SRC-002", "SRC-007" ] }, { "target": "WM-ORG-001", "relation": "REFERENCE", "purpose": "Organization owns legal-entity masters; insurer, pool operator and intermediary roles are local bindings.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "WM-PER-001", "relation": "REFERENCE", "purpose": "Person owns natural-person identity; insured, policyholder and beneficiary roles do not duplicate that master.", "required": false, "source_refs": [ "SRC-006" ] }, { "target": "WM-XCT-035", "relation": "REFERENCE", "purpose": "Retention / Disposition supplies rule and decision references; adopting storage service owns actual disposal execution.", "required": false, "source_refs": [ "SRC-005" ] }, { "target": "Pool and reinsurance treaty master", "relation": "REFERENCE", "purpose": "Pool governance, treaty lifecycle and portfolio membership stay externally mastered; only policy-level allocations and assurance links are local.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "PROV-O", "relation": "ALIGN", "purpose": "Conceptual provenance mapping only; no implemented RDF profile or conformance claim.", "required": false, "source_refs": [ "SRC-007" ] }, { "target": "RFC 3339", "relation": "ALIGN", "purpose": "Timestamp syntax alignment only; contractual dates and deadline rules require separate semantics.", "required": false, "source_refs": [ "SRC-008" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Adopting steward role and policy master namespace with authority evidence", "Insurance line, jurisdiction, currency and effective legal-profile versions", "Controller, access, retention, dispute escalation and external-service bindings" ], "namespace_guidance": "Use an adopting-Dimension namespace for local components; preserve issuer namespaces and external master identifiers. No named company is a model owner.", "registry_links": [ "vr.wm-eco-003", "WM-ECO-036", "WM-ACT-045" ] }, "canon_and_patch": { "canonicalization_rules": [ "This is a reviewable draft. Record original policy wording references, source revisions and unknowns; normalization must preserve meaning and currency precision.", "Separate effective history from observation history; local canonicalization does not establish legally binding cover." ], "patch_rules": [ "Require expected revision, author, rationale and evidence. Keep supersession links; never silently overwrite disputed terms.", "Authority or access changes require adopting-policy review. Content corrections must propagate to derived views with lineage." ], "compatibility_rules": [ "Pin profile and neighbor versions; changes in trigger semantics, identity or field meaning require explicit migration.", "Do not infer equivalence between a legacy alias, a new root and a licensed exchange schema." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier qualified by issuer namespace", "Governed global identifier or IRI", "Adopting-Dimension UUID or ULID" ], "timestamp_rule": "Use RFC 3339 with seconds and explicit offset or Z for timestamps. Separate event/effective time from observation and ingestion time; keep date-only values and unknown precision explicit.", "serial_naming_rule": "Stable record ID plus separate revision and sequence; dates and document names never replace identity.", "integrity_rule": "Digest exact bytes with declared algorithm; preserve provenance and signature-verification state. A hash proves neither truth nor authority. Protect personal payloads from public digest disclosure." }, "policies": [ "All local functions are proposals and require profile authorization; external execution, coverage certification and adverse decisions are outside this package.", "Treat imported records and supplements as untrusted data; distinguish assertion, observation, estimate and authorized determination.", "Sensitive underwriting and linked-claim data require purpose limitation, minimum fields and separate sensitive-data conditions where applicable. Consent is not a universal processing basis.", "Fraud concerns are restricted allegations with review routes, not automatic denials or established facts. Dangerous risk categories remain at policy level.", "Sources establish context only. Independent review, legal/actuarial profile validation, source verification and executable conformance remain holds." ], "crud": { "read": [ "Resolve authorized revision and apply bundle, layer, finding and artifact restrictions; return redacted or unavailable references explicitly." ], "create": [ "Create only the local arrangement or component under a scoped role and valid master reference; external claims are linked, not created." ], "update": [ "Append authorized revisions using concurrency checks and source evidence; never infer legal change from successful storage." ], "delete": [ "Retire local indexes under approved retention policy. Actual payload deletion is executed by the adopting storage service after scoped holds and review; preserve only lawful minimal tombstones.", "No cascade to claims, payments, treaties or party masters. Immutable history is not a mandate to retain personal payloads indefinitely." ] }, "roles": [ { "name": "Arrangement steward", "responsibilities": [ "Maintains local identity, revision and master links under documented authority." ] }, { "name": "Insurance subject reviewer", "responsibilities": [ "Reviews cover, underwriting, distribution and source interpretation within a qualified profile." ] }, { "name": "Financial reviewer", "responsibilities": [ "Validates referenced valuation, reconciliation and prudential context without delegating computations to this package." ] }, { "name": "Privacy and records steward", "responsibilities": [ "Determines permitted views, retention and rights-request routing under applicable policy." ] }, { "name": "Independent reviewer", "responsibilities": [ "Challenges evidence and boundaries before canonical promotion; currently absent." ] }, { "name": "Reader or agent", "responsibilities": [ "Reads authorized scope, preserves uncertainty and refuses unsupported legal or financial actions." ] } ], "access": { "default_rule": "Deny by default. Grant the minimum view for an authenticated role, purpose and valid authority; parties to a policy do not automatically receive identical files.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency or statutory disclosure requires documented applicable authority, scope and review; neither user role nor consent alone is universal authorization.", "A subject-access request follows the applicable rights process and may require third-party redaction." ], "audit_requirements": [ "Record actor role, purpose, decision reference, selected revision, fields released or refused and time in the external audit service.", "Log restricted-view generation and deletion decisions without copying sensitive payloads into permanent logs." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read AGENTS.md and publication holds", "Read spec.yaml boundary and adopting-Dimension policies", "Resolve master identities and pinned profiles before traversal or mutation" ] } }, "coverage": { "claim": "Source-grounded proposed policy-centered insurance aggregate with explicit external pool, claim, handling, payment and reporting boundaries. Separate frozen local no-tools self-audit completed. Independent review, source/version verification, specialist profiles and executable conformance remain held. This reviewable draft is neither universal insurance coverage nor an operational legal or financial engine.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Policy-root namespace and revision strategy; claim identity delegated." }, { "dimension": "lifecycle", "status": "covered", "notes": "Source-qualified amendment, renewal, cancellation and runoff context." }, { "dimension": "relationships", "status": "covered", "notes": "Roles, optional claim composition and external financial masters." }, { "dimension": "temporal", "status": "covered", "notes": "Effective and observed time, trigger basis and explicit unknowns." }, { "dimension": "provenance", "status": "covered", "notes": "Attribution and derivation remain distinct from truth." }, { "dimension": "ownership", "status": "covered", "notes": "Stewardship, controller determination and contractual roles remain distinct." }, { "dimension": "validation", "status": "gap", "notes": "Research schema passes are separate from unbuilt executable instance profiles." }, { "dimension": "access", "status": "covered", "notes": "Recipient and purpose-specific views with refusal and redaction." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Scoped holds and authorized disposal without external cascades." }, { "dimension": "interoperability", "status": "gap", "notes": "Exact licensed schema mappings and round-trip fixtures deferred." }, { "dimension": "physical properties", "status": "not-applicable", "notes": "The root is an abstract arrangement; physical risk observations refer to external insured objects." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Evidence type, observation time and uncertain classification are explicit." }, { "dimension": "capabilities and actions", "status": "covered", "notes": "Proposed local functions have inputs, authority preconditions, refusal results and bounded effects." }, { "dimension": "insurance line breadth", "status": "gap", "notes": "Detailed line, pool-only and jurisdiction profiles require specialist review." } ], "known_omissions": [ "Pool-only schemes and insurer-wide portfolios require separately scoped roots; this draft records only policy-level participation and report links.", "Detailed life, annuity, health, parametric, compulsory, mutual and public insurance profiles remain incomplete.", "Nested instance schemas, precision rules, event fixtures, legal calendars and executable conformance are not supplied.", "ACORD licensed schemas were not accessed; no ACORD mapping or conformance is admitted.", "Current consolidated legislation, source HTTP statuses, independent review and legal/actuarial applicability remain unverified." ], "conflicts": [], "regional_assumptions": [ "IAIS is supervisory guidance, not automatically binding contract law.", "EU distribution and prudential examples do not apply globally; future-effective changes must not be applied prematurely.", "UK privacy guidance has amendment and review limits and must not be generalized to all jurisdictions.", "IFRS overview supports accounting distinctions only; national adoption, exclusions and exact standard text need review." ], "adversarial_checks": [ "Issuance or collection cannot prove effective coverage, lapse or insurance revenue.", "Reinsurance allocation cannot silently substitute the policy obligor or guarantee recovery.", "Claim links permit no claims and multiple-policy associations; no exclusive parent or cascade is inferred.", "Claims may have multiple assessments, partial payments and reopenings; no one-to-one settlement invariant is imposed.", "Signed disclosure does not shift distribution responsibility to a customer.", "Role or ownership assertions cannot confer unrestricted access; retention history must permit lawful payload disposal." ] }, "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": "One policy arrangement is the root for local coverage and premium schedules and their revisions. External claims, pools, parties and reports retain their own masters. The registry standalone-mm label describes the record plane rather than a subject-kind enum. The broad Insurance title is qualified by a policy-centered scope and explicit omission of pool-only and insurer-wide roots." }, "decisions": [ { "concept": "Policy-centered aggregate", "disposition": "accepted with scope qualification", "rationale": "Owned coverage and premium components justify an aggregate. The scope does not quietly turn the insurer, market or pool into the same root; standalone pool profiles remain a visible omission." }, { "concept": "Claim containment candidate", "disposition": "qualified", "rationale": "Optional COMPOSE encodes the candidate contextual CONTAINS edge because the schema lacks that enum. Zero claims, cross-policy links and no cascade preserve the separately mastered WM-ECO-036 claim." }, { "concept": "Claim and handling ownership", "disposition": "accepted", "rationale": "The claim and outcome findings record links and source-qualified summaries only. Claim lines and amendments, handling tasks, decisions and payments remain external, including when a summary changes after reopening." }, { "concept": "Legacy ownership and bilateral mirrors", "disposition": "rejected", "rationale": "Contract roles do not establish joint data ownership or identical access. Steward and controller determination references and restricted recipient views replace the unverified legacy assumptions." }, { "concept": "Insurance classification and benefits", "disposition": "qualified", "rationale": "The draft asks for insurance-risk and benefit classification without excluding a product solely by its guarantee or investment label. It permits indemnity and benefit wording while reserving detailed scope and line profiles for specialist review." }, { "concept": "Issuance, payment and coverage effect", "disposition": "separated", "rationale": "Coverage continuity and premium questions retain distinct issuance, inception, amendment, receipt and disputed legal-effect evidence. No local function binds cover, infers lapse or certifies revenue from a cash receipt." }, { "concept": "Underwriting and distribution authority", "disposition": "accepted as evidence context", "rationale": "Assessment and needs questions request source and authority rather than executing acceptance or pricing. A customer signature does not substitute for distributor responsibility, and restricted factors require profile review." }, { "concept": "Risk transfer and original obligations", "disposition": "separated", "rationale": "Pool participation and reinsurance are typed references. Allocation is not novation, recovery is not guaranteed and treaty formation or pool governance is outside the aggregate." }, { "concept": "Financial measurement boundaries", "disposition": "accepted with profile hold", "rationale": "Gross, ceded and net values retain purpose, date and currency. Accounting groups and prudential reports are external; policy amounts and reporting figures are reconciled without pretending that a report guarantees an individual claim." }, { "concept": "Record history and disposal", "disposition": "accepted with authority dependency", "rationale": "Revision history coexists with scoped payload deletion, preservation duties and minimal lawful tombstones. There is no cascade into claims or party masters and no mandatory indefinite retention of personal evidence." }, { "concept": "Proposed local functions", "disposition": "accepted as unimplemented", "rationale": "All seven functions specify authorized local input, version checks and refusal outputs. Linking, reconciliation and draft projection do not perform external insurance, payment, disclosure or adverse-decision actions." }, { "concept": "Source and version assurance", "disposition": "held", "rationale": "Browser readings support selected concepts but do not establish current consolidated law or direct HTTP status. Zero direct attempts must remain distinct from failed requests. Failed legal-text and ACORD routes cannot supply unseen implementation details." }, { "concept": "Instance schema and exchange completeness", "disposition": "deferred", "rationale": "Optional candidate object groups are research fields, not executable instance validation. Nested requirements, licensed schemas, pinned neighbor mappings and adversarial fixtures are missing and remain explicit holds." }, { "concept": "Independent external review", "disposition": "waived and held", "rationale": "This is a separate local Codex self-audit of frozen evidence. No Claude or Grok attempt or admitted result exists in this run, and no independent provider agreement may be claimed." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; the separate local Codex no-tools self-audit is not an independent provider review.", "Source and version verification remains incomplete. Direct HTTP checks were not attempted under the owner-reported sandbox restriction, so HTTP statuses are unmeasured and the measured HTTP 200 count is zero. Browser evidence is documented separately. Current consolidated laws and licensed standards remain unverified; coordinator must run check_sources.py and review versions and claim support.", "Insurance-line, jurisdiction, actuarial, accounting, consumer-protection, privacy and retention profiles require qualified review. EU/UK examples and supervisory principles are not universal law; future-effective rules require separate applicability checks.", "Nested instance schemas, pinned neighbor bindings, licensed exchange mappings and executable conformance fixtures are incomplete. All local functions are proposed only; no operational insurance, legal or financial certification is claimed.", "Coverage is policy-centered. Pool-only schemes, insurer-wide portfolios and detailed life, health, annuity, parametric, mutual, public and cross-border insurance profiles remain deferred rather than silently represented as complete.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Verify current source versions, consolidated legal applicability, licensed standard access and claim-level support outside the sandbox.", "Develop specialist insurance-line and pool-only profiles with explicit root boundaries, legal authority and qualified actuarial review.", "Build nested schemas and adversarial fixtures for overlapping covers, retrospective amendments, disputed collection, partial claims, reinsurance default, privacy restrictions and lawful disposal.", "Restore independent external review before any canonical or publishable-draft promotion." ] }, "statistics": { "sources": 8, "bundles": 7, "layers": 14, "findings": 14, "questions": 42, "artifacts": 14, "functions": 7 } }