{
  "title": "Nonmetallic mining support test request data for AI",
  "source_page": "https://fiund.com/industries/nonmetal-mining-support-test-request-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A proposed scope revision is not an authorized test result",
    "context": "A support-provider exercise separates a request, approval and resulting report. All test names and measurements are invented, and no testing procedure is provided.",
    "records": [
      [
        "NM1",
        "Approved request N-3 revision A",
        "Authorizes measure J for specimen P under scope A."
      ],
      [
        "NM2",
        "Proposed request N-3 revision B",
        "Would add measure K for specimen P; approval field blank."
      ],
      [
        "NM3",
        "Fictional result R-9",
        "Reports J=6 practice units for P, referencing approved revision A. Another request N-4 names specimen Q."
      ]
    ],
    "question": "Which request scope does R-9 support, and can it be presented as completion of revision B or the separate specimen-Q request?",
    "answer": "NM3 explicitly references specimen P and approved revision A, so it supports the authorized J result in NM1. NM2 proposes adding K but contains no approval or K result. R-9 therefore does not establish completion of revision B. N-4 concerns Q, for which no matching result is supplied. Request, authorization and completion should retain separate states.",
    "failureModes": [
      "Selecting the alphabetically latest revision without checking its approval state.",
      "Reusing P's result to close Q's separate request because the test name is similar."
    ],
    "fields": [
      [
        "Request version and approval state",
        "Keeps proposed scope distinct from authorized scope."
      ],
      [
        "Requested versus reported measure",
        "Makes an absent K result visible."
      ],
      [
        "Specimen identity",
        "Prevents cross-request reuse of P's observation."
      ],
      [
        "Report's explicit request reference",
        "Preserves the documentary link used in the answer."
      ]
    ],
    "holdout": "Approve revision B after R-9 was issued but supply no new report. The correct answer should recognize the new authorization while leaving the added K work unverified.",
    "boundary": "Exclude actual client authorizations, procedures, contracts, locations, specifications and quality results. This fictional packet makes no operational testing recommendation."
  }
}