Monthly impact methodology

Your Monthly Compute impact report explains accepted work, participating Mac capacity, provider-community value, and the energy basis for a reporting period. It is distinct from a usage statement, an invoice, a payment receipt, and a Lithi Receipt, and it does not use any of those records as a substitute for its own evidence.

What the report separates

The report groups its evidence into four areas. Work completed covers accepted jobs, accepted natural units, service categories, result acceptance, billed amount, and the reporting period. Mac contribution covers distinct Macs, provider accounts, and provider owners used, with Mac contribution hours reported separately from a simple headcount, since one Mac, one account, and one owner are never treated as interchangeable.

Geographic business region reports your broad business region, a bucketed count of participating Macs in that region, the share of accepted work completed there, and the evidence state and privacy threshold behind that figure. Lithi never publishes a town, postcode, coordinates, address, device ID, provider identity, exact node location, or internal topology.

Provider-community contribution reports the provider pool allocated and settled, the number of provider accounts represented, the current signed allocation-policy version, and the authoritative settlement read-back state; allocated and settled values are always kept separate.

Environmental information and the baseline rule

The environmental section can report measured or estimated energy used, operational emissions, embodied-emissions allocation where supported, hardware reuse hours, method version, confidence, uncertainty, and the emissions-factor source and date.

Carbon saved, data-center work avoided, hardware purchases prevented, and any other net environmental benefit are shown only when a documented, comparable baseline supports the claim for that period. Where that baseline evidence is missing, the report shows that field as unavailable; it never shows zero and never states a saving without the baseline behind it.

Missing evidence is unavailable, never zero

Every field in the report's contract is measured, estimated, withheld, or unavailable, and the method section states which category applies. A field with missing evidence renders Unavailable for this period. Lithi does not substitute a zero, an estimate outside its stated confidence, or an old period's figure for a value the current evidence spine does not support.

The required evidence spine runs from the accepted job or result, through the execution attempt and the bound Mac identity, through privacy-safe region policy and provider account or owner aggregation, through the allocation record and Mercury settlement read-back, to the energy or emissions methodology and the signed monthly customer projection. A report can only state what that spine currently proves.

What this review covers

Limits

An impact report is not a usage statement, an invoice, a payment receipt, or a Lithi Receipt, and none of those records can be substituted for it. A measured or estimated field is scoped to the stated method and period; it does not generalize to another period or account.

Primary action

Review your Compute impact report

Related links

• Review results and receipt evidence
• Review provider allocation and settlement