{
  "title": "Remodeling change-order records for AI workflow evaluation",
  "source_page": "https://fiund.com/industries/residential-remodeling-change-order-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A homeowner request still needs the recorded decision owner",
    "context": "An entirely fictional remodel has an original task, a reported condition and two change-order versions. The practice rule requires approval by the named decision owner before a change is marked authorized.",
    "records": [
      [
        "RC1",
        "Practice scope and rule",
        "Task T4 covers panel replacement. Rule A names project lead Morgan as change approver."
      ],
      [
        "RC2",
        "Observation and message",
        "Reviewer reports a hidden mismatch. Homeowner message requests an added trim change; no Morgan approval attached."
      ],
      [
        "RC3",
        "Change-order history",
        "Version 1 proposes +3 practice cost units and +1 day. Version 2 proposes +4 and +2 days; both approval fields blank."
      ]
    ],
    "question": "What requested scope and proposed effects are documented, and what should the assistant do before presenting the added trim work as approved?",
    "answer": "RC2 documents the condition report and requested trim change. RC3 supplies two proposed cost and schedule summaries, with version 2 proposing +4 units and +2 days. Neither version records the approval required by RC1. The assistant should flag the authorization gap and route it to Morgan under the fictional rule, while identifying the proposed figures as estimates rather than accepted commitments or completed work.",
    "failureModes": [
      "Treating a homeowner request as the approval required by the stated project rule.",
      "Combining version 1 and version 2 effects instead of preserving their alternative proposed scopes."
    ],
    "fields": [
      [
        "Original and changed task",
        "Makes the scope difference inspectable."
      ],
      [
        "Decision owner and approval record",
        "Shows who can resolve the fictional authorization gap."
      ],
      [
        "Versioned cost and schedule effects",
        "Keeps summaries tied to the proposal that generated them."
      ]
    ],
    "holdout": "Record Morgan's approval for version 1 after version 2 was drafted. Ask which version is authorized rather than assuming the latest draft was approved.",
    "boundary": "Use invented people, values and rules. Exclude real contracts, addresses, access details, customer communications, payment information and architect drawings."
  }
}