Dispatch is our own project tool, not a client's. Five releases went out on 8 and 9 November 2026, and none of the code was written by hand. The review caught a money bug that would have reached a customer's invoice: 99.99 on the export, 100.00 on the report.
We left the ownership gates off this product on purpose, so it stays the honest place to count mistakes. The seats below are how those five releases ran. A seat is a charter. A person or an agent can fill it, and the charter stays the same.
The problem
A billing report that is a penny off is not a display glitch. Three 20-minute entries at 100 an hour should total 100.00, and the report did, while the export said 99.99 because the export rounded each entry and the report rounded each task. Anyone reconciling the two would find a number that does not match, and the smaller one is the one that looks like the detail.
Version 0.30.0, 0.31.0 and 0.32.0 went out on 8 November, and version 0.33.0 and 0.34.0 went out on 9 November, with 0.34.0 adding a client list, rates and the billing report.
What was built
Each release went through the same loop: a plan, a challenge, a simplify pass, a pull request, a review in a separate session with an independent verifier and none of the builder's context, end-to-end tests, a merge pinned to the commit that was reviewed, a copy-only backup, and then the deploy.
The rate work is one function. It resolves the rate, and there is a test for each rate rule, so a new rule cannot ship as a special case in the report and a different special case in the export. Billing is owner-only. A member of the project does not see a dollar figure.
The penny fix is one change to the export. Each line is the next step of that task's running rounded total, so the lines add up to the figure the report already shows, and rounding happens once on the way up instead of again on the line.
Principal Consultant
The consultant signs for the change and owes the explanation the same day. On Dispatch the ownership drill was left out of the loop on purpose, so a miss stays visible. A green suite is not the signature. The person who signs still has to say why the same three entries came out as 99.99 on one file and 100.00 on the other.
What a client gets from this seat is that explanation, in their own words, before the file goes out.
Business Analyst
Version 0.34.0 had to do three things, and it had to do them the same way every time: keep a client list, apply a rate, and produce the billing report. Done meant one function for the rate, a test for each rate rule, and a billing scope only the owner can open.
The challenge on that work sits before the build. The review is what caught the penny.
PMO
Five releases in two days is a tracking problem before it is a coding problem. Each release stayed a whole loop, and shipping one did not waive the review on the next. The record is the versions and the dates: 0.30.0, 0.31.0 and 0.32.0 on 8 November, then 0.33.0 and 0.34.0 on 9 November, each merged on its own reviewed commit.
Developer
The developer did not type the code. The diff still had to match the plan, and the person signing still had to explain it. The fix did not add a second rounding pass to hide the penny. It took the second rounding out. The running total is rounded as the task accumulates, and each exported line shows that step, so rounding the line on its own is what brings the penny back.
Code Reviewer
The reviewer worked in a separate session and did not inherit the builder's reasons. The builder does not close the reviewer's finding. The reviewer is who caught 99.99 against 100.00.
A total shown as exact, when the same entries were rounded on another path, reads as finished when it is not. The reviewer's job on this one was to read both paths. That read is what put 99.99 against 100.00.
QA
The end-to-end suite ran on the commit that was going to merge, and it did not run against production. A passing run proves only what it asserts. The rate function has a test per rule. The penny was caught in the review.
Still open
Three Azure decisions are still waiting: the subscription, the budget ceiling, and the login provider. Two product findings, both graded Low, are still open. The five releases are live. Those decisions are not.
Ask for the Review: https://databusiness.ai/contact