{
  "title": "Office procedure version histories for training AI assistants",
  "source_page": "https://fiund.com/industries/office-procedure-version-history-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A changed approval role makes an older office instruction insufficient",
    "context": "An original records-request procedure uses fictional roles and dummy documents. It contains no client record, invoice, personnel detail, contact or system access.",
    "records": [
      [
        "OP1",
        "Procedure v1",
        "Through day 9, original mock records requests require approval from role DESK-A."
      ],
      [
        "OP2",
        "Procedure v2",
        "Effective day 10, replaces DESK-A with DESK-B. A stated exception for historical requests requires supervisor clarification; no automatic carryover rule."
      ],
      [
        "OP3",
        "Request R",
        "Created day 8 with DESK-A approval, reopened day 12 for a changed document scope. No DESK-B approval or supervisor clarification supplied."
      ]
    ],
    "question": "Which procedure explains the original approval, and what should the assistant flag for the reopened request?",
    "answer": "OP1 explains R's original day-eight DESK-A approval. OP2 controls the day-12 period and changes the required role to DESK-B while leaving historical-request exceptions for supervisor clarification. OP3 also changes scope and supplies neither that clarification nor a new approval. Cite both versions and route the authority gap rather than assume the old sign-off covers reopened work or silently authorize a records action.",
    "failureModes": [
      "Answering from an obsolete approval role because it appears in a familiar procedure.",
      "Assuming a historical approval automatically covers a changed, reopened request."
    ],
    "fields": [
      [
        "Procedure version and effective interval",
        "Selects the rule."
      ],
      [
        "Request creation, reopening and changed scope",
        "Defines the event."
      ],
      [
        "Approval role and exception evidence",
        "Identifies the unresolved authority."
      ]
    ],
    "holdout": "Use a procedure change to retention period instead of role. Require retrieval of the changed field and its effective date without copying the earlier role-based answer.",
    "boundary": "Use independently authored procedures. Exclude actual client records and account access; authorized owners review any proposed real data package."
  }
}