No Demos. Ever.

There's a rule in our constitution that predates most of the product line: we do not build demos. We build the real thing.

A demo is a piece of software whose only job is to be believed. It doesn't have to survive real data, real users, or a second visit — it has to survive a twenty-minute call. That's why demos are always impressive and products so often aren't. The demo was the deliverable.

So our showrooms work differently. When you open one of the operating systems from the store, you're inside the actual product — the same code a paying customer runs — loaded with seeded example data so you have something to click on, and always showing the top tier, because you deserve to judge the best version. Nothing in it is staged. If a button exists, it does the thing.

The rule has a quieter half that matters more: a feature that's built but waiting on a key or a go-decision is allowed to exist dormant — honestly labeled, doing nothing. What's never allowed is fake-and-pretending: simulated success, hardcoded results, a spinner that always lands on good news. And nothing here gets called done until it's been verified live, with our own eyes, at the public URL. Internally, claiming something works when it doesn't is the gravest violation in the system — the whole operation runs on the difference.

This is what "craft first, claims last" means in practice. We'll always say plainly what's live and what isn't. The store is the proof: everything on it marked live is enterable right now, unsupervised, by you.