Read a receipt
What a run receipt records, how the verifier's verdict differs from the receiver's decision, and how cost reads when part of it is unknown.
On this page
A run receipt shows the full cost of one commissioned run in one document. It joins records that other parts of Hypervibe keep, owns none of them and changes none of them. It is put together on the machine that commissioned the run.
Four facts stay separate, and the receipt shows each #
| Fact | Recorded by | What it never means |
|---|---|---|
| Request (the commission) | You, before work starts | That the work succeeded |
| Job receipt | Reactor, for each build or verification job | A verdict; it counts as evidence only when it carries the recipe's own exit status |
| Verdict | A verifier other than the producer | Acceptance |
| Disposition | The receiver named in the commission | A verdict; the two are recorded apart |
A receipt lists every attempt and every cost line #
A receipt names the run and its commission, the revision the run started from, the candidate it produced, the verdict and the disposition. It lists every attempt in order, including failed, cancelled and unknown ones, each with its model calls, its jobs and a cost line for each. Costs that match no attempt, such as planning calls, are listed separately and still count. The receipt states how far it read the usage records; a later receipt that read further replaces it.
The verdict says what the verifier found #
| Verdict | Mark | Meaning |
|---|---|---|
| pass | ✓ | The verifier ran the commission's fixed recipe on the exact candidate, and every required check passed |
| fail | × | It ran, and a required check failed; the verdict names what failed |
| inconclusive | ⚠ | It ran, but the evidence does not decide: an input or test was missing, the base moved, it timed out or an outcome stayed unknown |
| error | ⚠ | Verification never reached a result, for example because it was refused or a worker was lost; it says nothing about the candidate |
| not checked | · | No verdict exists, because there is no candidate or no verifier has recorded one; this is how a missing verdict is shown, never a stored verdict, and never shown as a pass |
The disposition is the receiver's decision #
| Disposition | Mark | Meaning |
|---|---|---|
| awaiting acceptance | … | No disposition yet: the receiver has not decided, and a pass alone reads this way |
| accepted | ✓ | The receiver accepted this exact candidate |
| rejected | × | The receiver rejected it, with one reason and optional short text |
A disposition is accepted or rejected, and it names the receiver and the exact candidate it applies to. Awaiting acceptance is the absence of one, never a third decision.
A rejection names one reason #
| Reason | When the receiver picks it |
|---|---|
| needs revision | The result is close; the commission is revised and gets a new id |
| incorrect | The change does the wrong thing |
| wrong target | It is aimed at the wrong repository, branch, file or objective |
| insufficient evidence | The verdict or evidence does not let the receiver decide |
| not needed | The work is no longer wanted |
| other | None of the above, or the surface could not offer a choice; the text says why |
Each cost line is settled, estimated or unknown #
| State | Carries | Comes from |
|---|---|---|
| settled | An amount | Final settlement by the owner of the money |
| estimated | An amount and its basis | A list price for the tokens used, or a rate for a job's measured resources |
| unknown | A reason, and no amount | Any line with neither |
A settlement always wins over an estimate. A line is unknown when no usage was recorded for a call, when a request was sent but its usage has not been read yet, when no price exists, when a job has no receipt, when nothing rated a finished job, or when a job has not ended.
Totals never hide what is unknown #
Settled and estimated amounts are summed separately and never added into one figure. A sum with no lines behind it is empty, never 0. A receipt is complete only when no line is unknown; an incomplete receipt shows its known parts and the number of unknown lines, never a total. A model call served by a subscription has no cash price per call, so its list price is an estimate, not cash.
Run receipt · commission c-0117
Candidate a41f9c2 on base 0e77b18
Verdict ✓ pass
Disposition … awaiting acceptance
Attempt 1 inference settled $0.48
inference unknown sent, usage not read yet
verification unknown job not rated
Attempt 2 inference estimated $0.14 · list price
Totals settled $0.48 · estimated $0.14 · 2 unknown · incompleteHeld money is reserved, not settled #
Budgets read three figures: settled is final spend, held is money reserved on active holds, and remaining is the limit minus both. A reservation is a hold, not settled cost, and spend whose outcome is unknown stays held until it is reconciled. While usage is still settling, the Result card reads "cost pending".
Where to go next #
- First verified change shows where the receipt appears in the first run.
- Reactor explains jobs, job receipts and verification.
- Throttle explains settlement, budgets and holds.
- Glossary defines the product's words.