{
  "title": "Document preparation and accessible reading-order data for AI",
  "source_page": "https://fiund.com/industries/document-preparation-reading-order-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A visually correct two-column page can associate a note with the wrong extracted field",
    "context": "An original document-design fixture is described through intended and extracted sequences. No actual PDF export is claimed in this text packet; it specifies a reproducible evaluation to construct with owned content.",
    "records": [
      [
        "RO1",
        "Intended layout",
        "Left field A: preferred delivery day, note 'weekdays only.' Right field B: box color, no note. Original intended order A, A-note, B."
      ],
      [
        "RO2",
        "Correct extraction fixture",
        "Sequence: A prompt; weekdays-only note; B prompt. Tag-parent map places note under A."
      ],
      [
        "RO3",
        "Misordered fixture",
        "Same visual arrangement, extracted sequence A prompt; B prompt; weekdays-only note. Tag-parent map incorrectly places note under B."
      ]
    ],
    "question": "Which fixture preserves the note's intended field, and why should a visually inferred correct answer be scored separately from correct extraction?",
    "answer": "RO1 and RO2 attach the weekdays-only note to delivery-day field A. RO3's extraction and tag-parent map attach it after and under box-color field B, violating the intended association despite an unchanged visual arrangement. A model might infer the intended meaning from the rendered page, but that would not demonstrate correct extraction or tag structure. Score field association, extracted order and visual interpretation as distinct checks on the constructed document.",
    "failureModes": [
      "Accepting a semantically guessed answer as proof that the extracted reading order is correct.",
      "Assigning a note to the next extracted prompt instead of its intended field."
    ],
    "fields": [
      [
        "Field ID and intended note parent",
        "Defines semantic ownership."
      ],
      [
        "Visual position and tag-parent sequence",
        "Separates appearance from structure."
      ],
      [
        "Extraction output and scoring dimension",
        "Makes the failure reproducible."
      ]
    ],
    "holdout": "Move the note visually while retaining its correct A tag parent. Require the structural check to remain correct and evaluate visual interpretation separately.",
    "boundary": "Use original text and graphics with construction provenance. Exclude client forms, signatures and private metadata."
  }
}