Cost receipts and approvals

A receipt is an actual (a metered charge or a provider's bill), an estimate (a modeled amount) or a refund. Its basis says how the amount was reached: metered-llm from a model call's usage at a known rate, member-rate from a person's time at an hourly rate, modeled from a formula, or provider-bill from an invoice line. The case's cost section shows measured charges, refunds, estimates and other currencies as separate rows, and an amount in another currency is never converted.

An estimate entered by hand names its rate and its hours, and the amount must equal the two multiplied; a window, when given, is two instants in order. An estimate with none of that is still an estimate, and is never promoted to a measured amount by the passing of time.

A charge that several cases share lands on each as a share: a fraction between zero and one, the parent record it is a share of, and the parent's amount, with the share's amount equal to the parent's times the fraction. A case never carries more than its part; a case that already carries the parent does not add the share again, and a run priced against a prevention package is not counted again against its incident.

A receipt whose rate is not known is counted as unpriced and given no amount. A case with no receipts has no cost recorded, which the section says in words. A validation run's cost lands on the case as an actual and an estimate kept apart, and a hosted run's usage is shown as three lines, priced, estimated and pending the provider's reconciliation, never summed.

An approval is a fingerprint over the action, the files, the brief, the target and the policy version. A fix applies only while its scope produces the same fingerprint; change a file, the target or the policy and the approval no longer applies, and the fix waits for a new one. The digest the desktop verified is recorded before the approval, so an approval pushed in the same snapshot binds to what was checked. A drafted fix that cannot clear builds, tests and the guard replay is not shown at all; verified recovery lists the eight checks.

The desktop app pushes the receipts its remediation loop measured; a person enters an estimate, a refund or a share on the case; a validation run lands its own. Each carries its actor and time. Receipts are keyed by source record, so rereading the same meter replaces that source's row; a separate correction can be recorded as a refund or a new receipt. The economics of a home, the cases that carry a receipt with their measured and estimated totals apart, is what the LLM cost metrics home lists.

• Verify a recovery before approval.
• Inspect local cost telemetry.
• Review held actions in the approval queue.