GratisAI household · reconcile register differences across one assumed meter rollover · local-first FREE TIER 1 Free Run Available
dial-rollover stub · punched ticket stubs

Reconcile Register Differences Across One Assumed Meter Rollover

A mechanical register can show a smaller number later because it wrapped. Keep that assumption and the register multiplier visible before treating a subtraction as a utility-consumption record.

1 · Register code | earlier whole reading | later whole reading | units per register increment

FIRST-LOAD

HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.

Data note: The dial-rollover stub processes Register code | earlier whole reading | later whole reading | units per register increment locally. Starter/sample selection and Run compute in this tab; no input is sent by the calculator. A local draft may be saved; explicit state-link sharing or optional external AI formatting can disclose inputs. Use non-sensitive labels.

Perspective: Before: a lower later display looked like negative usage. After: the modulus, scale and one-wrap assumption explain the reconstructed increments explicitly.

2 · Read the dial-rollover stub

Single-cycle register arithmetic only, not bill validation or meter-fault diagnosis. Ask the utility to confirm register modulus, multiplier and any reset or replacement; do not use this model when multiple cycles or reverse motion are possible.

Optional filing controls are a local prototype.

Checkout is unavailable. The reading above is complete; print, CSV and five local summaries are optional enhancements, not hidden answers.

Before using the dial-rollover stub

The modulus is one above the largest display value: a register showing 0 through 9,999 has modulus 10,000. Both readings are whole values below that modulus, and the multiplier converts one register increment to one common output unit. Rows may be summed only when they are disjoint registers expressed in the same unit, not a gas reading mixed with electrical energy or overlapping submeter totals. The model assumes forward motion and a difference of less than one full cycle between readings. A lower later display invokes one rollover; an equal or greater display invokes none. Replacement, reset, reverse motion and multiple cycles are not inferred. Confirm actual unit conventions and meter history before using the result in a bill discussion.

Boundary and sources

Single-cycle register arithmetic only, not bill validation or meter-fault diagnosis. Ask the utility to confirm register modulus, multiplier and any reset or replacement; do not use this model when multiple cycles or reverse motion are possible.

Mechanism: competence-autonomy-loop

Optional AI formatting, never the calculation

Manual entry completes this dial-rollover stub for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.

Format only these fictional or non-sensitive notes for a dial-rollover stub. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string", "string"]}], "setting": "string"}. The columns are Register code | earlier whole reading | later whole reading | units per register increment; the setting is Register modulus (one above its largest display). Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.

An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.