How we work

Decisions get written down before they get built.

There is a repository that is not code. It holds the purpose, the principles, the architecture, and every significant decision — what was chosen, what was rejected, and what evidence would reverse it. Where a decision and the code disagree, one of them is a bug.

• Doctrine over convention

  A root document defines why the company exists. Everything below it must be reconcilable with it — or it wins and the lower document is amended, on the record.

• Reversal conditions

  A decision that cannot say what evidence would overturn it is a preference wearing a decision's clothes. Ours name it.

• Corrections, not rewrites

  When a record turns out to be wrong, it gets a dated correction rather than a silent edit. The history of being wrong is the useful part.

• Say what is actually built

  Doctrine forbids claiming a capability before it ships. That rule governs this website too, which is why every product here carries an honest status.

A curated public view of it is coming. In the meantime, roles on our careers page name the specific documents that govern them, and we will send them to anyone who asks — the repository itself is private, and pointing you at a door you cannot open would be worse than saying so.