{
  "title": "District steam and chilled-water meter records for AI",
  "source_page": "https://fiund.com/industries/district-thermal-meter-period-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Reconcile a practice register across a documented replacement",
    "context": "Artificial meter counters demonstrate period and identity checks. The figures are not customer consumption, bills or equipment readings.",
    "records": [
      [
        "METER-A-SEGMENT",
        "First practice interval",
        "At endpoint X, meter A increases from 70 to 90 counts during days 1–14."
      ],
      [
        "REPLACE-X",
        "Confirmed practice mapping",
        "Meter B replaces A at endpoint X at the start of day 15, with no uncovered interval in this exercise."
      ],
      [
        "METER-B-SEGMENT",
        "Second practice interval",
        "B increases from 0 to 12 of the same stated count unit during days 15–28."
      ],
      [
        "METER-C",
        "Unrelated endpoint",
        "Endpoint Y has a value of 35 with no documented unit or measurement basis."
      ]
    ],
    "question": "What counter increase is documented for endpoint X across days 1–28? Can C be included in the same comparison?",
    "answer": "A contributes 90 minus 70, or 20 counts. B contributes 12 minus 0, or 12. The supplied replacement map and matching unit support a 32-count increase across X's two covered intervals. Adding the ending register values would give the wrong quantity. C belongs to another endpoint and lacks the required basis, so it cannot be included in that comparison.",
    "failureModes": [
      "Adding cumulative ending registers instead of interval increases.",
      "Joining the replacement to the wrong endpoint.",
      "Combining a value whose unit and measurement basis are missing."
    ],
    "fields": [
      [
        "Endpoint and meter mapping",
        "Preserve which instrument served which endpoint and interval."
      ],
      [
        "Start and end registers",
        "Retain both observations needed for each delta."
      ],
      [
        "Unit and continuity",
        "Document the shared basis and the absence or presence of a coverage gap."
      ]
    ],
    "holdout": "Remove the first reading for B. The endpoint total should become unresolved for that segment instead of assuming a zero reset.",
    "boundary": "The counters and mapping are fictional. Keep real service layouts, consumption, billing terms, configurations and live-system details outside the exercise."
  }
}