{
  "title": "Veterans program form and instruction version data for AI",
  "source_page": "https://fiund.com/industries/veterans-program-form-revision-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "An archived instruction does not establish the portal's current form requirements",
    "context": "An invented veterans-program office has original generic change-of-contact forms. The packet contains no actual agency form, veteran, claim, medical history or benefits decision.",
    "records": [
      [
        "VF1",
        "Archived practice form F1",
        "Issued day 1; attachment A required. Old instruction page still points to F1."
      ],
      [
        "VF2",
        "Current-listing record day 10",
        "Lists F2 issued day 8; requires A plus new attachment B. F2 expressly replaces F1 for the practice listing."
      ],
      [
        "VF3",
        "Dummy packet inventory",
        "Contains F1 and A only; no individual submission, receipt, acceptance or decision record supplied."
      ]
    ],
    "question": "Which version and attachments does the current listing specify, and what can the packet establish about an individual application?",
    "answer": "VF2 specifies F2 with A and B as the current practice requirements and expressly supersedes F1. VF1's archived instruction remains evidence of the older version rather than the current listing. VF3 lacks F2 and B under that comparison, but contains no actual application or agency action. Report the version mismatch without inferring submission, acceptance, eligibility or any individual's benefits outcome.",
    "failureModes": [
      "Following an archived instruction while ignoring the current-listing revision.",
      "Treating a document inventory as proof of an actual application, acceptance or benefits decision."
    ],
    "fields": [
      [
        "Form revision and issue date",
        "Identifies the document instance."
      ],
      [
        "Current-listing authority",
        "Separates portal status from archived links."
      ],
      [
        "Required and present attachments",
        "Makes the practice completeness gap inspectable."
      ],
      [
        "Application-event availability",
        "Limits claims about any individual case."
      ]
    ],
    "holdout": "Provide F2 and both attachments but still no submission record. Require a complete-practice-packet finding without calling it submitted or accepted.",
    "boundary": "Use original mock forms and layouts. Exclude veteran identities, medical information, claims, service histories and actual personal-data forms."
  }
}