The token chart is not a receipt
The last lesson ends in a room. You read the roll-up out loud. GO or NO-GO, with named blockers. Then someone — finance, the sponsor, the person who signed the builder spend — asks the question the roll-up does not answer: what did we get for the week?
The answers that arrive by default are watermelons wearing a dollar sign. A token chart. A "40% faster" slide with no named function under it. A company-wide savings figure nobody in the room can recompute. Those numbers are fluent, and they die the first time a CFO asks "which hours, whose rate, what shipped." Fluency is not a receipt. You already know that about citations. It is also true about value.
This is not a different discipline from the rest of the chapter. Spec, gate, and roll-up already refused vibes as evidence. The receipt is the same refusal, aimed at the value question. Hours and dollars count when they attach to one function, counted the same way before and after, at a loaded rate finance already defends, with a name on the row and an accepted deliverable behind it. Anything larger than a staff-meeting table is a claim you cannot stand next to.
What the receipt is for
A loaded rate is not a number you invent. Finance already has one — the fully loaded hourly cost they use for contractors and headcount models, salary plus benefits plus overhead. You ask for the rate they already put on paper this quarter. If they have not published one, the receipt is blocked. You do not fill the gap with a blog-post average, and you do not multiply a guess across the company.
The hours are the same kind of artifact as an acceptance check: observable, same unit, same person or seat, same week. "The team feels faster" is A3 from lesson one. "Weekly RAG roll-up used to take four hours and now takes one" is A1. The first cannot survive a stranger. The second can.
This lesson builds that gate: a row is either READY — hours, dollars, owner, shipped — or BLOCKED, with the missing pieces named. The staff-meeting total sums only the READY rows. That is the whole policy, and it is small on purpose. One function you can defend this week beats a company-wide slide you cannot.