{
  "title": "Solid waste pickup completion and service exception data for AI",
  "source_page": "https://fiund.com/industries/solid-waste-pickup-status-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A recovery-visit completion supports a stop while a facility receipt supports only its load",
    "context": "Three fictional route events use a dummy service location and inert references. No actual route trace, household, worker footage or collection operation is represented.",
    "records": [
      [
        "WP1",
        "Scheduled stop S",
        "Day 2 visit V1 marked missed with exception E. Schedule alone contains no completed service event."
      ],
      [
        "WP2",
        "Recovery visit",
        "Day 3 V2 explicitly references S/E; signed mock completion confirms the recovery stop."
      ],
      [
        "WP3",
        "Transfer receipt",
        "Facility receipt acknowledges aggregate load L on day 3. No stop-level contents or S-to-L membership supplied."
      ]
    ],
    "question": "Which record supports service at the dummy stop, and what separate fact can the facility receipt establish?",
    "answer": "WP2 explicitly links V2 to the missed stop S and exception E, supporting a completed recovery visit on day three. WP1 remains the original missed event. WP3 independently documents receipt of load L, but lacks a stop-level map and cannot prove S's service by itself. Preserve the original exception, recovery and aggregate handoff as separate events rather than use a facility load receipt to imply every scheduled stop was completed.",
    "failureModes": [
      "Overwriting a missed visit with a later recovery instead of preserving both events.",
      "Using an aggregate facility receipt as proof of an individual stop's completion."
    ],
    "fields": [
      [
        "Stop, visit and exception reference",
        "Defines the service history."
      ],
      [
        "Recovery link and signed completion",
        "Supports the later event."
      ],
      [
        "Load receipt and membership scope",
        "Limits aggregate attribution."
      ]
    ],
    "holdout": "Remove V2's S/E link while retaining the same date. Require the recovery attribution to become unresolved despite a plausible sequence.",
    "boundary": "Use invented locations and original records. Exclude actual routes, households and customer data; clear any separate capture rights in advance."
  }
}