← MyStatus

The same week, priced two ways

2026-08-23 to 2026-08-30. One invoice by the hour, one by what is actually scarce, and the reason we are changing.

Two invoices for the same seven days. The first is the one our billing report actually printed, priced by the hour. The second prices the same week by the two things that are genuinely scarce here. We are switching to the second, and the first is on this page because an argument for a new way of charging is worth nothing without the old bill sitting next to it.

Old way

Priced by the hour

Time the work log was open — 45.3 hrs billed
$6,795.00
Of 47.9 hours measured; every line floors to a tenth, so 2.6 hours were worked, logged and not charged. Produced by running npm run report -- --since 2026-08-23 --until 2026-08-30 --evidence and captured .

The document itself is at the foot of this page, unedited — every line, and the public entry behind every hour. It is the last invoice this operation prices by the hour.

Proposed way

Priced by what is actually scarce

Owner attention — 51.6 hrs
$7,740.00
Stated, not measured here: from a run over the session records on the owner's own machine, counting a stretch as ended after 15 minutes of silence. That policy is a choice, not an observation, which is why it is printed beside the figure. At $150.00 an hour.
Machine work — one week
$50.25
Stated, from the owner's bill: a flat $217.75 a month, twelve payments spread over fifty-two weeks. Not an estimate standing in for the machine's cost — it is the entire bill for the whole machine workforce for the week.

Line entries are basically the same as the invoice above — the deliverables did not change; the meter did.

PricedMeasureAmount
Owner attention51.6 hrs$7,740.00
Machine workone week of the flat plan$50.25
TotalAgainst $6,795.00 the old way.$7,790.25

Measurement to follow: the same week's tokens at published list rates. We expect it to show that the flat plan is a bulk discount, and it is not estimated here — a page arguing that the machine bill belongs on the invoice cannot invent the one figure that would settle how big it should be.

The old way charged $6,795.00 for this week and called it hours. The honest bill is slightly higher — and over 99% of it is human attention. The machine that let one human run two work streams at once is the cheapest line on the invoice. That is what changed.

Why the second one exists

Hours of operation are evidence. They are not the price. The invoice below is real and every line of it opens onto a public entry. It is still the wrong thing to charge for, and this run is where that stopped being arguable.

Look at the two clocks in it. The week logged 47.9 hours of building and 36.8 hours of business and product work, and the combined wall clock is 68.3 hours — so 16.4 hours had both logs open at once. Nobody worked two jobs in one hour. Two streams of work ran side by side, which is what happens when part of the workforce is a machine.

That is the whole problem with hours as a price. A workforce that is part machine can run more of them in parallel whenever it likes, which means the seller can dial the number. A number the seller can dial is not a price, it is a lever — and what cannot be dialed is the owner's attention, one person with one clock, and the machine bill, which arrives whether anyone is watching.

$50.25 of AI tokens let one coordinator run business tasks and technical tasks at the same time. Done the old way — do one task, wait for it to finish, start the next — the same work would have filled 84.7 hours of calendar. It filled 68.3. Hourly billing punishes exactly that: deliver faster, bill less. So we don't bill the 84.7, and we don't bill the 68.3 either — we stopped billing hours at all. The speedup is priced where it belongs: in the deliverables, delivered sooner, and in the fact that exploiting AI to its fullest is rewarded instead of punished.

The invoice, verbatim

The old way's invoice, exactly as the tool printed it on . Nothing below this line has been edited, and it is never regenerated.

Its first three lines are work from the evening before this week began. The tool asked git for everything since the 23rd, and git answered in universal time, where a New York evening on the 22nd has already become the 23rd. That was fixed on 6 September 2026 and the same command now prints three fewer lines. These three stay, because an invoice is evidence exactly as far as nobody went back and touched it.

This capture is from Aug 23–30 and predates the 2026-09-07 fix; it under-lists 22 merges that shipped with no measurable window. Later captures carry them as a counted line.

Every line is a change merged in this period. Every hour is a pair of timestamped rows on a public log, posted as the work happened — not reconstructed afterwards. Rate: $150/hr (stated 2026-08-26).

DeliveredMergeHoursAt $150/hr
Timestamps now read in the reader's own clock, paired with UTCdbb7fbf0.0$0.00
The stats page stops explaining itselfb5a26d50.0$0.00
Stale data after server restart: found and fixed4ac759e0.0$0.00
Representations plan review folded in: every open question but one settled67b84320.0$0.00
Two field notes from the representations review, approved by Tom33113110.0$0.00
Permalink pages now fetch a window around the cited update instead of the task's entire history6fbc93d0.0$0.00
A link label was white-on-cream and unreadable in dark modebf1d9d70.0$0.00
One item, one branch970ca6a0.0$0.00
The stats page's OPEN sign gets a real design, and two git rules get earned the hard way1b71b680.0$0.00
The stats page's "am I working right now" sign now reads a real record34d8b910.7$105.00
The stats page now shows what the tooling costs before any work startsff1ac462.1$315.00
The last work entry folds away, like the downtime log9ccd8ec0.1$15.00
The stats page's session figure becomes a range, from two measured tasksa17d1f50.1$15.00
This session finishes writing down its own record69d50dc0.0$0.00
The Work Log's design finally lives in a document, and a task's numbers mean what they saya064c391.8$270.00
The crash gets a recovery prompt, and the crashed night gets an honest recordda0ed350.0$0.00
The Coding Right Now sign on our stats page used to read OPEN or CLOSED — a state name answering a question nobody printed. It now answers the question: YES or NO. The record behind it doesn't change; the note under the sign explains which entries produced the answer.69f02331.1$165.00
The stats page now carries a second sign next to Coding Right Now: Working on Biz Stuff, read from a public task that tracks the non-coding work — the thinking, business, and marketing sessions. Same machinery, same honesty rules; both signs can be lit at once, and the page says so.0c5356c0.0$0.00
The rule for how the business stream gets its entries is now on the record: when the day's thinking session opens, beats, wraps, or stops, and which of those posts need approval. Docs only — the stream itself started posting yesterday; this writes down the discipline it follows.516d80f0.1$15.00
The new business sign shipped wearing the coding sign's explanation, and one word in it was false — it said work ends when it merges, and the business stream has no merges; its sessions wrap. Each sign now speaks its own stream's language, and the business sign moved into a section of its own, ready for the business numbers to join it.23890770.1$15.00
The idea behind the two signs is now written into the product record instead of living in one day's conversation: if machines take over the coding, and coding is the only work anything tracks automatically, everyone else's day reads as empty. The answer is that any tool a person uses can post what happened — the chat app, the word processor, even the desk phone — and the reason that isn't surveillance is structural, not a promise: the worker owns the record, holds the key, and posts outward by choice.b69e4980.5$75.00
The stats page now says what this actually costs to run — $375.69 a month, $776.39 so far, broken out line by line — plus how many conversations have happened about it and how many demos have been given. What's deliberately missing is any measure of how interested anyone seemed: that's a grade about other people rather than an event about our own work, and at six conversations it would name people who never agreed to be named.122e4890.7$105.00
The rule for measuring what a task cost now insists on both ends of the window, and on never writing a number the measuring tool didn't just print — both learned from one entry that got its figures wrong twice the same afternoon. Also adds this session's field note: facts don't lean, and the truth is always good to know.867fbf60.0$0.00
Say what the published cost figure leaves out, and where the salaries went91a8b850.3$45.00
The work log records which Claude model did each task17e1b800.9$135.00
The stats page now shows the tasks its own cost figures came from, and which model ran each one948ed7b1.9$285.00
Every page carries the site footer, from the layout7e051571.7$255.00
The server can now tell an app it is out of date56b7a750.7$105.00
Updates can be sealed against editing, but never against deletion868495f0.2$30.00
The about page now says what Tom actually reviews69a880d0.4$60.00
The about page says "helps me" now, not "help me"352bff60.0$0.00
Don't tidy the seams: the mismatched screenshot as proof25629ab0.0$0.00
The stats page stops claiming line-by-line review8db445a0.1$15.00
The Android app can now be told it is too old to keep running4a3d9691.7$255.00
The iPhone app can now be told it is too old to keep running93454521.1$165.00
Hours on the record: /stats publishes how long the work has been opend9008f00.3$45.00
Session turns population — what we were actually counting76600a00.7$105.00
Store listings: one copy source, two cuts316f2d90.4$60.00
Store listings: four of six open questions answered722b2d20.0$0.00
The privacy policy discloses the push notification tokenb17fce80.4$60.00
The bold lead-ins get their space back4003a3e0.0$0.00
The record now matches reality on the spacing fix916edf10.0$0.00
The support URL now leads to a support paged803ca20.5$75.00
The iPhone app answers the encryption question once, in writing3ff7f7a0.1$15.00
The connector says when it is ignoring your keysfee78cf0.0$0.00
The task queue records how this one actually finished00d77ee0.0$0.00
Free accounts get a limit on how many tasks they can run at once7fe6d220.5$75.00
The limit on tasks becomes a limit on automation5e297892.0$300.00
The record catches up with the workce337430.0$0.00
What people actually use this for, written down the way they'd search for ite15ece20.2$30.00
The play-by-play use case was already on the recorde67dd130.0$0.00
What people use this for, and why we won't build a network to spread it9f10df40.6$90.00
The field note, in Tom's words, and three corrections to mine25e134e0.0$0.00
Who writes a field note, written down the way it actually worksa45b7a50.1$15.00
What it would have cost: the consulting-rate figure on /statse4b52850.9$135.00
What it would have cost — followup: the rounding note moves up a panel64b723f0.0$0.00
Stats headings say what they pricedbcfe6b0.6$90.00
The reader finally has a way in7a2e53d1.1$165.00
The Glass Factory: one link you can hand somebodyf58a8742.4$360.00
About becomes the product page; the sausage factory moves next door6a0bf761.3$195.00
The back-link remembers where you came ineeef9490.6$90.00
The new app icon lands on every surface37f473c2.1$315.00
The tooling runs on the product, and now the page says sof859b631.4$210.00
The owner's edits get read, gated, and landed58566700.2$30.00
Receipts on the dogfooding pagec587cf40.7$105.00
The dogfooding page stops sending you away9d4cb530.2$30.00
Not attributable to one deliverable—11.7$1,755.00
Total45.3$6,795.00

What the unattributed line is. Time the log was open outside any deliverable's window: the minutes between a task being opened and its first commit, review and approval waits after a change shipped, and sessions that produced nothing shippable. It is billed at the same rate and kept on its own line rather than spread across the ones above it, because spreading it would make every line a little bit invented.

47.9 hours were measured and 45.3 are billed. Every line rounds DOWN to a tenth of an hour, so the 2.6 hours in between are worked, logged, and not charged. The rounding only ever runs this direction.

Some lines are 0.0 hours. A change can ship inside this period with no logged time against it — the work happened before the period opened, or the whole branch lasted less than a tenth of an hour. The line stays visible rather than being dropped, because what shipped and what was billed are two different questions.

2 deliverables ran at the same time, so their lines can claim the same hour twice. The total does not — it counts overlapping time once.

Business and product time: 36.8 hrs, logged separately and deliberately not billed against any deliverable above. Both logs can be open at once; the combined wall clock for the period is 68.3 hrs.

Evidence

Timestamps now read in the reader's own clock, paired with UTC — dbb7fbf

The stats page stops explaining itself — b5a26d5

Stale data after server restart: found and fixed — 4ac759e

Representations plan review folded in: every open question but one settled — 67b8432

Two field notes from the representations review, approved by Tom — 3311311

Permalink pages now fetch a window around the cited update instead of the task's entire history — 6fbc93d

A link label was white-on-cream and unreadable in dark mode — bf1d9d7

One item, one branch — 970ca6a

The stats page's OPEN sign gets a real design, and two git rules get earned the hard way — 1b71b68

The stats page's "am I working right now" sign now reads a real record — 34d8b91

The stats page now shows what the tooling costs before any work starts — ff1ac46

The last work entry folds away, like the downtime log — 9ccd8ec

The stats page's session figure becomes a range, from two measured tasks — a17d1f5

This session finishes writing down its own record — 69d50dc

The Work Log's design finally lives in a document, and a task's numbers mean what they say — a064c39

The crash gets a recovery prompt, and the crashed night gets an honest record — da0ed35

The Coding Right Now sign on our stats page used to read OPEN or CLOSED — a state name answering a question nobody printed. It now answers the question: YES or NO. The record behind it doesn't change; the note under the sign explains which entries produced the answer. — 69f0233

The stats page now carries a second sign next to Coding Right Now: Working on Biz Stuff, read from a public task that tracks the non-coding work — the thinking, business, and marketing sessions. Same machinery, same honesty rules; both signs can be lit at once, and the page says so. — 0c5356c

The rule for how the business stream gets its entries is now on the record: when the day's thinking session opens, beats, wraps, or stops, and which of those posts need approval. Docs only — the stream itself started posting yesterday; this writes down the discipline it follows. — 516d80f

The new business sign shipped wearing the coding sign's explanation, and one word in it was false — it said work ends when it merges, and the business stream has no merges; its sessions wrap. Each sign now speaks its own stream's language, and the business sign moved into a section of its own, ready for the business numbers to join it. — 2389077

The idea behind the two signs is now written into the product record instead of living in one day's conversation: if machines take over the coding, and coding is the only work anything tracks automatically, everyone else's day reads as empty. The answer is that any tool a person uses can post what happened — the chat app, the word processor, even the desk phone — and the reason that isn't surveillance is structural, not a promise: the worker owns the record, holds the key, and posts outward by choice. — b69e498

The stats page now says what this actually costs to run — $375.69 a month, $776.39 so far, broken out line by line — plus how many conversations have happened about it and how many demos have been given. What's deliberately missing is any measure of how interested anyone seemed: that's a grade about other people rather than an event about our own work, and at six conversations it would name people who never agreed to be named. — 122e489

The rule for measuring what a task cost now insists on both ends of the window, and on never writing a number the measuring tool didn't just print — both learned from one entry that got its figures wrong twice the same afternoon. Also adds this session's field note: facts don't lean, and the truth is always good to know. — 867fbf6

Say what the published cost figure leaves out, and where the salaries went — 91a8b85

The work log records which Claude model did each task — 17e1b80

The stats page now shows the tasks its own cost figures came from, and which model ran each one — 948ed7b

Every page carries the site footer, from the layout — 7e05157

The server can now tell an app it is out of date — 56b7a75

Updates can be sealed against editing, but never against deletion — 868495f

The about page now says what Tom actually reviews — 69a880d

The about page says "helps me" now, not "help me" — 352bff6

Don't tidy the seams: the mismatched screenshot as proof — 25629ab

The stats page stops claiming line-by-line review — 8db445a

The Android app can now be told it is too old to keep running — 4a3d969

The iPhone app can now be told it is too old to keep running — 9345452

Hours on the record: /stats publishes how long the work has been open — d9008f0

Session turns population — what we were actually counting — 76600a0

Store listings: one copy source, two cuts — 316f2d9

Store listings: four of six open questions answered — 722b2d2

The privacy policy discloses the push notification token — b17fce8

The bold lead-ins get their space back — 4003a3e

The record now matches reality on the spacing fix — 916edf1

The support URL now leads to a support page — d803ca2

The iPhone app answers the encryption question once, in writing — 3ff7f7a

The connector says when it is ignoring your keys — fee78cf

The task queue records how this one actually finished — 00d77ee

Free accounts get a limit on how many tasks they can run at once — 7fe6d22

The limit on tasks becomes a limit on automation — 5e29789

The record catches up with the work — ce33743

What people actually use this for, written down the way they'd search for it — e15ece2

The play-by-play use case was already on the record — e67dd13

What people use this for, and why we won't build a network to spread it — 9f10df4

The field note, in Tom's words, and three corrections to mine — 25e134e

Who writes a field note, written down the way it actually works — a45b7a5

What it would have cost: the consulting-rate figure on /stats — e4b5285

What it would have cost — followup: the rounding note moves up a panel — 64b723f

Stats headings say what they price — dbcfe6b

The reader finally has a way in — 7a2e53d

The Glass Factory: one link you can hand somebody — f58a874

About becomes the product page; the sausage factory moves next door — 6a0bf76

The back-link remembers where you came in — eeef949

The new app icon lands on every surface — 37f473c

The tooling runs on the product, and now the page says so — f859b63

The owner's edits get read, gated, and landed — 5856670

Receipts on the dogfooding page — c587cf4

The dogfooding page stops sending you away — 9d4cb53

The old way's figures are from the captured run above, taken and never regenerated: the prose here reads numbers off that document, so replacing it would leave this page describing a week that is no longer on it. The proposed way's figures are the owner's, from his own bill and his own machine, and are marked as stated wherever they appear. The per-feature version of the same model — person hours and tokens, each linked to the entry it was measured from — is on the receipts page.