{
  "title": "Securities clearing and settlement status data for AI",
  "source_page": "https://fiund.com/industries/securities-clearing-settlement-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Clearing acceptance and settlement confirmation are distinct events",
    "context": "An inert transaction-stage fixture uses fabricated participant aliases and original status cards. It contains no position, bank detail or instruction capable of settling a transaction.",
    "records": [
      [
        "CS1",
        "Transaction T-A history",
        "Matched day 1; accepted for clearing day 2, event C-A. Correction C-A2 changes an internal dummy label, retaining T-A identity."
      ],
      [
        "CS2",
        "Settlement S-A",
        "Day 3 explicit settlement confirmation references T-A and C-A. No additional transaction created by the label correction."
      ],
      [
        "CS3",
        "Transaction T-B history",
        "Matched and accepted for clearing day 2. A settlement-reference field says pending; no confirmation document supplied."
      ]
    ],
    "question": "Which stages are evidenced for each transaction, and does the correction or pending reference establish another settled transaction?",
    "answer": "CS1 and CS2 support matching, clearing acceptance and a separately confirmed settlement for T-A. C-A2 changes a label under the same transaction identity and does not create another T-A. CS3 supports matching and clearing acceptance for T-B, but its pending reference is not a settlement confirmation. Report T-B's missing confirmation as a source gap rather than inferring settlement from progression through earlier stages.",
    "failureModes": [
      "Treating acceptance for clearing as proof of settlement.",
      "Counting a corrected event as a new transaction or a pending reference as a confirmed event."
    ],
    "fields": [
      [
        "Transaction and event aliases",
        "Preserves identity across stages."
      ],
      [
        "Stage, timestamp and source type",
        "Distinguishes acceptance from confirmation."
      ],
      [
        "Correction target and pending evidence",
        "Makes version and completion gaps explicit."
      ]
    ],
    "holdout": "Supply a T-B confirmation that references the wrong clearing event. Require a linkage exception before reporting the packet fully reconciled.",
    "boundary": "Use original offline cards. Exclude participant records, positions, access details and settlement instructions; this task initiates no transaction."
  }
}