{
  "title": "Corporate approval workflows as AI training and evaluation data",
  "source_page": "https://fiund.com/industries/corporate-approval-workflow-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Resolve an approval request under the subsidiary's policy",
    "context": "A fictional parent and subsidiary have different purchasing approval rules. The test asks the assistant to find the effective rule and the missing authorization, without making a real purchasing decision.",
    "records": [
      [
        "PARENT-P4",
        "Parent practice policy",
        "Parent requests up to 8,000 demonstration credits can be approved by a department manager. This policy expressly excludes subsidiary Harbor."
      ],
      [
        "HARBOR-H2",
        "Subsidiary practice policy",
        "Effective from day 10, Harbor requests above 3,000 credits require the regional director. Earlier Harbor requests follow H1."
      ],
      [
        "REQ-17",
        "Invented request",
        "Harbor requests 5,200 credits on day 12. Its department manager adds an approval comment."
      ],
      [
        "ROLE-17",
        "Original role register",
        "The commenter is a Harbor department manager. No regional-director approval or delegated authority is supplied."
      ]
    ],
    "question": "Does the provided package document the approval required for REQ-17? Cite the applicable rule and explain what evidence is still needed.",
    "answer": "HARBOR-H2 applies because the request belongs to Harbor and occurs after day 10. The request exceeds its 3,000-credit threshold, so the supplied rule calls for regional-director approval. ROLE-17 establishes only the commenter's manager role. The required approval is not documented in this package. PARENT-P4's higher threshold cannot be substituted because that policy excludes Harbor. A valid director approval or applicable delegation record would need separate evidence.",
    "failureModes": [
      "Applying the parent's amount threshold to an expressly excluded subsidiary.",
      "Treating any approval comment as evidence of the required role.",
      "Using the current policy without checking the request date and effective range."
    ],
    "fields": [
      [
        "Requesting entity",
        "Choose the policy belonging to Harbor rather than the parent."
      ],
      [
        "Request date",
        "Resolve whether H1 or H2 was effective for this event."
      ],
      [
        "Amount and practice unit",
        "Evaluate the stated threshold without treating credits as money."
      ],
      [
        "Approver role and delegation",
        "Separate a person's comment from demonstrated authority under the rule."
      ]
    ],
    "holdout": "Create an otherwise identical Harbor request on day 8 and supply H1 with a different role threshold. The correct answer must change because the effective policy changes, even when the amount and commenter stay the same.",
    "boundary": "The policy, organizations and request are fictional. No real spend is approved. A commercial workflow package must clear subsidiary ownership, employee information, internal policy restrictions and any privileged records before transfer."
  }
}