TITANOS

Demonblade Labs · Issue 012

My proof page now refuses numbers older than 30 days

If you publish numbers about your own work, this one is for you. It sells nothing and costs nothing to read. It is about my own site at TitanOS in Brisbane, so nobody else is named.

The rule

A number on a proof page is only true on the day you measured it. After that it is a memory. So the proof page on titanos.tech has a rule in code: any figure measured more than 30 days ago is not shown as a number. It is shown as UNKNOWN, with the date it was last measured, until someone measures it again.

The edge case

The rule had a test, but I hit its real edge this week. The headline work-rate figure came from my old job ledger, a count for 12 October of 1,630 finished jobs. That ledger stopped writing at 07:57 on 13 October. So there was no current reading to put beside it, and the figure was about to turn into UNKNOWN on its own.

Measured again

I took the honest route. I did not keep the old number alive and I did not leave a blank. I measured again, from a different record: the status file of every build lane.

The numbers

For the whole of 10 November, local time, 24 hours: 281 lanes finished. 278 are done and 3 failed. That is 11.7 an hour, a failure rate of 1.1 percent, and a median of 10.4 minutes from start to finish. The method is printed on the page: finished divided by 24, median taken from the latest start to the finish, a lane that failed and was re-run counted once on its final status.

The catch

One honest catch. This is a different record from the old ledger, so I do not draw a trend between 1,630 and 281. They count different things. The page says which record each number came from and on which date.

Retired, not blanked

Cards with no live source behind them were retired instead of left showing UNKNOWN: cost per day, token counts, the repository size and a few others. They are listed with the date each was last measured, so nothing disappeared quietly. A new test fails the build if any row older than 30 days is kept on the page.

The deploy

The same day, the site went live from a single tap on my phone. The tap approved one card. A cloud runner then built the site and ran the full test manifest, 151 of 151 passing, and published only that tested build. The previous version stays on a rollback branch, gh-pages-backup-20261111-1124, so going back is possible.

What is live and what is not

What is true right now, as a plan and not as done: the live site is the version from before the re-measure. The re-measured figures are on my main branch and publish with the next tap. Until then the live page does not have them.

Which number on your site would you be embarrassed to see dated?


Previous issues: Zero green in 58: I was tuning the wrong dial, Busy is not finished: 561 jobs done, and every final gate held, The ninth bug: my heartbeat went quiet when I needed it most, Eight bugs in a chain that was meant to run itself, Twelve blockers behind a green suite, The exam the builder never saw, The button that ignored a fast thumb, I built a product assistant that is not allowed to guess, I built a gym that judges its own best strategies as luck, I freed 334 gigabytes and the disk got smaller, Why more AI agents don't automatically mean more output. All issues: Demonblade Labs.