The standards we hold.
For everything we make.
These apply to projects, deliverables, and everything we ship — not as aspirations, but as standards. They're not negotiable on deadline, not softened because something is "just a prototype." If we made it, these apply.
Unpolished, still gems.
Our work is an unpolished jewel. We're early — no traction, no veneer, no permission to pretend otherwise. That shows, and that's fine. What isn't negotiable is what's underneath: the quality of what we build is a must, not a goal.
An unpolished gem is still a gem. A polished piece of glass is still glass. We know which one we are.
It can be ugly. It must do the work.
Robustness over aesthetics. A feature that works reliably — that handles edge cases, holds under load, does exactly what it says — is worth more than one that looks perfect and fails quietly.
We fix ugly. We can't always fix broken. Ugly and correct beats beautiful and wrong every time.
Detail is for the people who look.
Most people won't notice. That's fine. We don't put detail in for show — we put it in because the person who does notice is the person we're building for.
Detail is a signal. It says: someone cared enough to put it there. It's only visible to the people whose attention it deserves. Those are our people.
Scope is a decision, not a default.
Every feature we don't build is a feature that can't break, can't confuse, and can't slow us down. We choose what's in deliberately. We choose what's out with the same care.
The product gets smaller before it gets bigger. That's not a constraint — that's the principle.
Build for whoever is still using it in three years.
The launch is a moment. The software lives for years after. We don't optimize for the demo. We optimize for the version that's been running for three years and still works exactly as it should.
If we wouldn't want to maintain it, we shouldn't ship it.