{
  "title": "Business school office simulation data for AI",
  "source_page": "https://fiund.com/industries/business-school-office-simulation-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A correct attachment still needs the right handoff state",
    "context": "An instructor-owned office exercise uses invented document versions and recipients. No real message is sent; the model classifies draft artifacts against a fictional rule.",
    "records": [
      [
        "BS1",
        "Practice appointment change",
        "Meeting moves from Tuesday to Thursday. Authorized recipient role: coordinator. Attachment revision R3 supersedes R2."
      ],
      [
        "BS2",
        "Draft A",
        "Addressed to coordinator; body says Thursday; attachment is R2."
      ],
      [
        "BS3",
        "Draft B and handoff log",
        "Addressed to coordinator; body says Thursday; attachment R3. No send or receipt confirmation recorded."
      ]
    ],
    "question": "Which draft matches the current content requirements, and what evidence would be needed to call the handoff delivered?",
    "answer": "BS1 makes Thursday, role coordinator and attachment R3 the current requirements. Draft A matches the date and recipient but carries obsolete R2. Draft B matches all three content requirements. BS3 records no send or receipt confirmation, so content readiness does not establish delivery. Identify Draft B as ready for the stated review, while preserving its unconfirmed handoff status.",
    "failureModes": [
      "Calling Draft A correct because its message body has the updated date.",
      "Equating a correct saved draft with a delivered or acknowledged communication."
    ],
    "fields": [
      [
        "Effective appointment details",
        "Defines the current date being communicated."
      ],
      [
        "Attachment revision",
        "Catches a stale document despite a correct body."
      ],
      [
        "Authorized recipient role",
        "Makes the handoff target explicit."
      ],
      [
        "Draft, sent and acknowledged states",
        "Prevents readiness from becoming delivery evidence."
      ]
    ],
    "holdout": "Add a receipt for R2 from before the appointment change. Require the answer to explain why it does not confirm delivery of the revised R3 handoff.",
    "boundary": "Use original teaching prompts, invented participants and non-routable dummy addresses. Exclude student records, client files and actual internal communications."
  }
}