{
  "title": "Office copier lease meter data for AI reconciliation",
  "source_page": "https://fiund.com/industries/office-copier-meter-baseline-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A replacement copier starts a different meter history",
    "context": "Two invented copier aliases use arbitrary counter values. Device identity and separate color/mono counters matter even though a fictional service agreement continues.",
    "records": [
      [
        "OC1",
        "Old device A readings",
        "Day 1: mono 1000, color 200. Day 20 final: mono 1120, color 230."
      ],
      [
        "OC2",
        "Replacement record",
        "Device B replaces A on day 20; B installation baseline mono 10, color 5."
      ],
      [
        "OC3",
        "Device B later reading",
        "Day 30: mono 70, color 15. A's final reading remains attached to the same service-month folder."
      ]
    ],
    "question": "What counter differences are supported for each device, and why should the service-month folder not produce a single cross-device subtraction?",
    "answer": "OC1 supports A's differences of 120 mono and 30 color between its own readings. OC2 and OC3 support B's differences of 60 mono and 10 color from its installation baseline. A's 1120 is not B's starting mono value, despite the continuous agreement and shared folder. Keep device-specific intervals and counters separate; the packet supplies no pricing or authorized billing rule.",
    "failureModes": [
      "Subtracting A's final counter from B's day-30 reading and reporting negative usage.",
      "Combining color and mono counters without preserving their separate definitions."
    ],
    "fields": [
      [
        "Device alias and replacement event",
        "Marks the change in meter history."
      ],
      [
        "Counter type and baseline",
        "Defines compatible subtraction pairs."
      ],
      [
        "Reading time and provenance",
        "Keeps the service folder from overriding the device source."
      ]
    ],
    "holdout": "Add a verified counter reset on B between installation and day 30. Require the system to request a reset-aware interval record before repeating the earlier subtraction.",
    "boundary": "Use fabricated counters only. Exclude network details, print jobs, customer documents, actual meter exports, locations, rates and contract volumes."
  }
}