{
  "title": "Meter and counting-device data for AI counter interpretation",
  "source_page": "https://fiund.com/industries/meter-total-interval-counter-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A reset breaks the cumulative subtraction",
    "context": "A fictional meter export uses abstract counter units and an explicit reset event.",
    "records": [
      [
        "1",
        "Reading at 08:00",
        "M7 total 95 units."
      ],
      [
        "2",
        "Reset log",
        "09:00 reset; pre-reset total 100 and post-reset total 0."
      ],
      [
        "3",
        "Reading at 10:00",
        "M7 total 7 units."
      ]
    ],
    "question": "How many units accrued in the interval?",
    "answer": "The interval contains 5 units before reset (100 − 95) and 7 after reset (7 − 0), totaling 12. Records 1–3 supply both reset boundary values. Directly subtracting 95 from 7 would compare counters from different epochs.",
    "failureModes": [
      "Treating a reset as negative consumption",
      "Ignoring the pre-reset subtotal"
    ],
    "fields": [
      [
        "counter_epoch",
        "Separates totals across resets"
      ],
      [
        "reset_boundary_readings",
        "Support the two interval segments"
      ],
      [
        "interval_delta",
        "Stores increment rather than cumulative value"
      ]
    ],
    "holdout": "Omit the pre-reset value; report the known post-reset increment and flag the whole interval incomplete.",
    "boundary": "No actual utility accounts, meters, billing advice or customer usage data."
  }
}