{
  "title": "Background screening authorization scope records for AI",
  "source_page": "https://fiund.com/industries/background-check-scope-authorization-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A component request and a matching applicant key must both fit the supplied scope",
    "context": "A wholly fictional screening-document exercise uses abstract components and invented subject aliases. It contains no consumer report, investigative fact, biometric or employment decision.",
    "records": [
      [
        "BS1",
        "Practice request",
        "Subject DEMO-A: components C1 and C2 requested under request R."
      ],
      [
        "BS2",
        "Scope card",
        "Original fictional authorization names DEMO-A/R/C1 only. Later note says an update for C2 was requested, with no approval or revised card."
      ],
      [
        "BS3",
        "Other subject card",
        "Subject DEMO-B has a C2 scope card. Similar name to A but distinct subject key; no equivalence record."
      ]
    ],
    "question": "Which request component has matching scope evidence, and can the update note or other subject's card close C2's gap?",
    "answer": "BS1 and BS2 match C1 to DEMO-A and request R. C2 is requested but lacks corresponding approved scope evidence in the fixture; the later note records only that an update was sought. BS3 belongs to DEMO-B and cannot supply A's missing support. Return the component-level match and gaps for qualified review without deciding legal authorization, suitability for employment or whether any screening should occur.",
    "failureModes": [
      "Treating a requested scope update as an approved expansion.",
      "Matching a component while ignoring the subject key or inferring employment eligibility from paperwork."
    ],
    "fields": [
      [
        "Subject and request alias",
        "Defines the document scope."
      ],
      [
        "Requested versus supported component",
        "Makes partial matches visible."
      ],
      [
        "Update approval and missing source",
        "Limits the conclusion."
      ]
    ],
    "holdout": "Add a C2 card naming DEMO-A but a different request. Require request-scope review before treating it as R's support.",
    "boundary": "Use original mock documents. Exclude actual reports, identifiers and client forms; qualified people retain compliance and employment decisions."
  }
}