{
  "title": "Theme park attraction document records for AI",
  "source_page": "https://fiund.com/industries/theme-park-attraction-document-scope-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A similarly named review may cover another attraction version",
    "context": "Fictional attraction aliases and original document labels create an offline scope-matching task. There are no ride components, actual audits, repairs or operating decisions.",
    "records": [
      [
        "TP1",
        "Practice register",
        "Attraction A has document version V2; attraction B has V1."
      ],
      [
        "TP2",
        "Authorized review document",
        "Explicitly names A/V2 and review scope S. It makes no statement about B."
      ],
      [
        "TP3",
        "B daily-summary attachment",
        "File title resembles A's review, but body names A/V1. A separate B note says review requested, with no result."
      ]
    ],
    "question": "Which attraction/version has a matching review, and what do B's attachment and request establish?",
    "answer": "TP2 matches A/V2 in TP1 for the stated review scope S. TP3's attached document names A/V1, not B/V1, so its similar title and folder location do not establish B's review. The B note records a request only. Preserve attraction, document version and scope, and flag B's missing matching result for a qualified reviewer without declaring an attraction safe, repaired or approved to operate.",
    "failureModes": [
      "Matching review files by title while ignoring the attraction and version in the body.",
      "Treating a requested review as a completed audit or operating clearance."
    ],
    "fields": [
      [
        "Attraction and version",
        "Defines the reviewed subject."
      ],
      [
        "Review scope and authority",
        "Limits what the document actually establishes."
      ],
      [
        "Request versus result state",
        "Makes an unresolved handoff visible."
      ]
    ],
    "holdout": "Add a B/V1 document limited to administrative inventory rather than scope S. Require scope matching even when attraction and version now agree.",
    "boundary": "Use invented independent forms only. Exclude equipment details, plans, real audits, attendees, access controls, incidents and live safety information."
  }
}