Meter Reading and Replacement Ledger

How to use Meter Reading and Replacement Ledger

Start with the opening reading and one common unit. Enter each later read or replacement with any known wrap count; close old registers separately from new initial values and inspect exact interval usage plus date-based averages.

1. Use the example as the schema; replace its labels and entered model assumptions.
2. Start with the opening reading and one common unit. Enter each later read or replacement with any known wrap count; close old registers separately from new initial values and inspect exact interval usage plus date-based averages.
3. Calculate, inspect the complete witnesses and limitations, then copy or download the JSON report.

Good to know

• 1–200 uniquely labeled events on strictly increasing dates in 1900–9999. Readings and an optional positive modulus are exact decimal strings from 0 to 1,000,000,000 with six places. Values must be below a supplied modulus; wrap counts are whole 0–100.
• Without a modulus, wraps must be zero. A replacement requires both the old final and new initial reading. Declining values without enough declared wraps are refused. Same-date replacements/reads are outside the date-based averaging profile.
• No calibration factor, unit change, inferred hidden wraps, utility account, meter accuracy, leak/safety diagnosis, tariff, tax or assurance that an actual bill is correct. Readings remain authored evidence, not verified measurements.
• Local calculation with no upload, input persistence or outside lookup. Model JSON is limited to 30,000 characters and 10,000 values. Decimal quantities are strings with up to six places; count fields use plain JSON integers. Exact fractions are capped at 8,192 bits. The complete JSON output is limited to 1,000,000 characters; approximate numbers preserve their stored values. Unsupported states fail explicitly.