Fuel Refill and Range Ledger

How to use Fuel Refill and Range Ledger

Start with your entered tank balance, add each chosen refill, then deduct distance multiplied by that leg’s litres-per-100-km assumption. Check capacity, fuel feasibility, reserve flags and separately rounded purchase receipts.

1. Use the example as the schema; replace its labels and entered model assumptions.
2. Start with your entered tank balance, add each chosen refill, then deduct distance multiplied by that leg’s litres-per-100-km assumption. Check capacity, fuel feasibility, reserve flags and separately rounded purchase receipts.
3. Calculate, inspect the complete witnesses and limitations, then copy or download the JSON report.

Good to know

• 1–200 distinct ordered legs. Tank capacity, opening/reserve/refill litres and distance kilometres are at most 1,000,000; capacity and each consumption rate must be positive. Rates and per-litre prices are at most 10,000. Quantities are exact decimal strings with up to 6 places.
• Refill occurs before the row’s leg. Overfilling or consuming unavailable fuel refuses the model. A zero-distance row can record a purchase. Reserve is an entered review threshold, not a safety standard. Display currency is a label with 2 decimal receipt rounding, without currency conversion.
• Only purchased fuel has a known entered price. Starting fuel valuation and consumed-fuel cost are not invented. No route, gas station data, current prices, taxes, weather, measured vehicle efficiency or real driving-range assurance.
• 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.