{
  "title": "Life insurance rider version records for AI review",
  "source_page": "https://fiund.com/industries/life-policy-rider-version-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A signed rider's effective period differs from an unactivated proposal",
    "context": "A fabricated policy packet contains original clause labels, inert IDs and no insured person. It evaluates document association rather than the meaning or adequacy of life-insurance coverage.",
    "records": [
      [
        "LR1",
        "Policy P-A base card",
        "Original practice clause label BASIC applies from day 1. No beneficiary, payment or health fields included."
      ],
      [
        "LR2",
        "Signed mock rider R1",
        "References P-A; effective day 20; replaces clause label BASIC with EXTENDED under the exercise's stated version rule."
      ],
      [
        "LR3",
        "Other papers",
        "Proposal R2 for P-A would use label PLUS but is unsigned and never activated. Signed R3 belongs to similar ID P-A2."
      ]
    ],
    "question": "Which clause label has a document-version basis for P-A on days 15 and 25, and do R2 or R3 alter that selection?",
    "answer": "LR1 supplies BASIC for day 15 because LR2's rider does not become effective until day 20. For day 25, LR2 explicitly changes P-A's label to EXTENDED under the fixture's version rule. LR3's R2 is an unactivated proposal and R3 belongs to P-A2, so neither changes P-A's selected document. Report the cited text and dates without determining actual coverage or interpreting an insurance contract.",
    "failureModes": [
      "Applying a signed rider before its effective date.",
      "Treating an unsigned proposal or another policy's rider as an active amendment."
    ],
    "fields": [
      [
        "Policy alias and rider target",
        "Establishes document identity."
      ],
      [
        "Execution state and effective period",
        "Separates proposals from operative fixture versions."
      ],
      [
        "Replaced clause and source citation",
        "Limits the documented change."
      ]
    ],
    "holdout": "Remove R1's signed mock copy and retain only its proposal. Require the current-version conclusion to become unresolved rather than assuming execution.",
    "boundary": "Use original invented clauses and invalid IDs. Exclude actual policy forms, customers, health and underwriting information; qualified staff retain coverage review."
  }
}