{
  "title": "Event ticket reservation, transfer and price records for AI",
  "source_page": "https://fiund.com/industries/ticket-reservation-transfer-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A transfer invitation and its acceptance apply to individual tickets",
    "context": "An original ticket-agency mockup uses inert references and no event art, scannable code, customer or transaction. Prices are invented document fields.",
    "records": [
      [
        "TK1",
        "Reservation R1",
        "Two dummy tickets A and B; stated total 80 practice units. Original price card explicitly names R1."
      ],
      [
        "TK2",
        "Transfer events",
        "Invitations sent for A and B. Acceptance event explicitly references R1/A only; no B acceptance supplied."
      ],
      [
        "TK3",
        "Other price and refund note",
        "Price card for R2 shows total 70. Refund request names R1/B but no approval, settlement or completed refund event."
      ]
    ],
    "question": "Which transfer is documented as accepted, which price belongs to R1, and what refund state can be reported?",
    "answer": "TK2 supports acceptance of R1/A's transfer and only an invitation for R1/B. TK1 provides R1's stated 80-unit total; TK3's 70 belongs to R2 and cannot replace it. TK3 records a B refund request without settlement evidence, so the refund remains requested rather than completed. Keep ticket-level transfers, reservation-level price and refund workflow separate without making a legal entitlement or actual payment conclusion.",
    "failureModes": [
      "Treating all invitations as accepted because one ticket has an acceptance.",
      "Using another reservation's price or promoting a refund request to completed reimbursement."
    ],
    "fields": [
      [
        "Reservation and ticket reference",
        "Defines event scope."
      ],
      [
        "Stated price source",
        "Preserves the matching total."
      ],
      [
        "Invitation, acceptance and refund event type",
        "Separates stages."
      ]
    ],
    "holdout": "Add an acceptance for R2/B. Require R1/B to remain pending despite the same local ticket letter.",
    "boundary": "Use original interfaces and nonfunctional references. Exclude real tickets, customer data and partner pricing systems; clear third-party artwork separately."
  }
}