The screens we shipped empty

This is the sample post. It exists so the journal has a working template: copy this file, change the front matter above, and write. Delete it, or the sample tag, whenever the real library arrives.

---

There’s a moment in every product review meeting where someone says the empty screen is a problem. They’re usually right. An empty screen doesn’t retain anyone. It doesn’t demo well. Investors flinch at it.

We had that meeting, in a manner of speaking, and decided the empty screen was the product.

What the full screen costs

Software that fills every view on day one has to get the filling from somewhere, and there are only two sources: someone else’s data dressed up as yours, or a template dressed up as an insight. Either way, the app is talking before it has listened, which is the exact quality we find unbearable in people.

The moment an app tells you what your Tuesday means, you start living toward the telling. You may notice the evidence for it and quietly discard the rest. The label writes the diary.

What the empty screen buys

Patience, mostly. And one strange asset that compounds: everything Kizmit ever shows you is something your own record put there. A pattern that took eight weeks to surface is worth more than a forecast that took zero, for the same reason an earned reputation is worth more than a bought one.

Here’s the kind of thing Kizmit does show from day one, because it’s just true:

The moon’s actual phase. The pressure. The sky. The same facts for everyone, printed the way an almanac would print them, meaning nothing until your record says otherwise.

An oracle is never empty. That’s how you know it’s an oracle.

The template part

Posts in this journal are MDX files. Front matter at the top: title, description, date, tags, and a draft flag that keeps a post out of the build entirely. Below it, prose, with headings, lists, blockquotes, and rules all styled to the house tokens:

• Serif headings in Libre Baskerville, hierarchy by size and italic
• Body in Hanken Grotesk at reading size
• Mono details where data wants labeling

That’s the whole machine. Copy, retitle, write.