← notebook

A gauge, never a deadline

2026-08-19

I built this app around one rule, written before it had a name: it has to lower a tired parent's stress, and it must never say the child has to sleep at 14:20. Not only because that would be unkind. Because it would be a lie with a clock on it.

Here is what a precise predicted time actually does inside a home. It stops being information and turns into an appointment. The appointment gets missed — children are not trains — and the miss gets read as a verdict on the parent. I have caught myself doing it. The number was mine, I wrote the code that produced it, I know exactly how soft it is, and I still felt the small sting when the day disagreed. If it stings me, holding the source, what does it do to someone who assumes the app knows something they don't?

A model whose own test error is measured in tens of minutes has no business printing a minute-precise appointment.

So the hero of the screen is a gauge and a wide, soft window. Exact times exist — I am not hiding numbers — but they sit in the second row, where detail belongs. When a window passes, the app answers in calm amber and recoverable language: carry gently, aim a little earlier next time. No alarm red. No countdown. Nothing that ticks.

The part I like most is that none of this is a concession. It is the honest reading of the science. The two-process model supports windows, not points, and my error bars are tens of minutes wide. Printing a minute would be precision theater — dishonest and stressful. Rigor and mercy usually pull in opposite directions and you have to choose one. Here they point at the same design, and I intend to keep the app standing on that spot.

Everything else in this notebook is a footnote to this rule.