{
  "title": "Surety bond scope records for AI testing",
  "source_page": "https://fiund.com/industries/surety-bond-scope-change-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A project amendment and a bond-change request do not prove the same state",
    "context": "Two invented projects have original scope cards and clearly marked nonoperative bond examples. There are no contractors, indemnities, financial statements or actual instruments.",
    "records": [
      [
        "SB1",
        "Project A packet",
        "Contract A-v1 scope X; amendment A-v2 scope Y. Mock bond BA initially cites A-v1."
      ],
      [
        "SB2",
        "Confirmed change",
        "Original practice confirmation BA2 explicitly links BA to A-v2 and replaces the A-v1 reference."
      ],
      [
        "SB3",
        "Project B packet",
        "Contract B-v2 exists. Bond BB still cites B-v1; a draft request asks to change it. Another project has bond BB2, with no B reference."
      ]
    ],
    "question": "Which project has a confirmed corresponding bond-reference change, and which packet needs further verification?",
    "answer": "SB2 explicitly updates BA's reference to A-v2, aligning the Project A packet's contract revision and bond-change record. SB3 shows a B-v2 contract amendment but only a draft request to change BB, leaving its B-v1 reference unreconciled. BB2 belongs to another project and cannot supply that confirmation. Identify the document mismatch and missing authorized change without determining bond liability, enforceability or coverage.",
    "failureModes": [
      "Assuming a contract amendment automatically updates the separately recorded bond reference.",
      "Treating a draft change request or another project's similar bond ID as confirmation."
    ],
    "fields": [
      [
        "Project, contract and bond aliases",
        "Defines the association."
      ],
      [
        "Scope revision and cited contract version",
        "Exposes version alignment."
      ],
      [
        "Change request versus confirmation",
        "Separates proposed and documented updates."
      ]
    ],
    "holdout": "Supply a confirmation for BB that changes a spelling field only. Require the B-v1 contract-reference mismatch to remain open.",
    "boundary": "Use original fictitious forms labeled nonoperative. Exclude indemnities, project plans and claims; qualified staff retain contractual judgments."
  }
}