Cash, capacity and modeled upside
The three ledgers, why they are never summed, and how unknown, zero and negative stay three different results.
Three ledgers
A benefit is recorded in one of three ledgers, each in its own unit, each with its own evidence rule. The product keeps them on separate lines on every screen, in the weekly email and on every page of the PDF.
| Ledger | Unit | What it is | In the grade |
|---|---|---|---|
| Cash | $ | A supported financial change attributable to AI after disclosed adjustments, with the relevant AI cost for the same scope and period deducted. | Yes |
| Capacity | hours | Time or output improvement, shown in hours or operational units, with its baseline, quality and attribution assumptions. | As time value |
| Modeled upside | $ estimate | Scenarios: possible extra revenue, structural change. Never realized return. | No |
Why they are never summed
- They are different units. Hours plus dollars is not a number. Time value is dollars, but it is dollars that did not arrive; the label not cash is the whole point.
- They rest on different evidence. A cash claim can be traced to a general-ledger credit and attested. Freed hours rest on a baseline and an acceptance assumption. Upside rests on a scenario nobody has lived.
- A loaded hourly rate does not turn freed time into cash. Nobody's payroll fell because a task got faster, unless someone decided it should, and that decision is a cash event of its own.
- A total would be read as a return. Oabo's promise is a finance-reviewable answer; a headline that mixes realized, imputed and hoped-for value cannot be reviewed.
Note
The rule is enforced in code, not in copy. The front end warns in development if any single figure is handed both a cash amount and an hours value, and the PDF renders the three as separate bars that are never stacked.
Unknown, zero and negative
Missing measurement, measured zero and measured loss are three results and render differently everywhere:
| State | Shown as | Means |
|---|---|---|
| Unknown | Not entered | Nobody typed it. Nothing is assumed. The grade waits or counts the use case out, and says which. |
| Claimed none | None claimed | Benefits were entered and this one is not among them. A real zero claim. |
| Zero | $0 / 0.0 h | A measured or stated zero. Rendered as a figure, not as a blank. |
| Negative | -$150, a loss of $2.50 per $1 of cost | Keeps its minus sign in every figure and multiple, and in the letter. |
| Not estimable | Not estimable | In Scenario analysis: an input the scenario needs is missing. Never zero. |
Estimated, Measured, Verified
On the Scorecard, each benefit carries a confidence worked out when it is read, from the evidence linked to it. A use case takes its lowest benefit; the workspace sentence names the lowest across the month.
| Confidence | When |
|---|---|
| Verified | The benefit is linked to a value claim that is final-attested (audit signed off). |
| Measured | Linked to a validator-confirmed value claim, or to a guided-proof claim with a source on record. |
| Estimated | Anything else, including every benefit the owner typed and every benefit with staff-reported hours cited beside it. |
Linking changes the confidence, never the amount. How a claim earns each state is in How evidence is approved.