How we build.
Standards and principles we use to make product, design and engineering decisions. They are not universal rules: they are criteria the team maintains and evolves.
01
Criteria, not rules.
02
Written from practice.
03
Maintained as a team.
01
Engineering
Code is always reviewed
No change reaches main without a second pair of eyes.
Boring over clever
We pick the solution anyone on the team can maintain at 3am.
02
Product
The problem before the solution
Nothing gets built without explaining what problem it solves and for whom.
Measure before opining
Product decisions are argued with data, not with hierarchy.
03
Design
Tokens, not values
No hardcoded colors or radii: everything comes from the design system.
Accessible by default
Contrast, visible focus and keyboard support are not optional.
04
AI
AI proposes, the team decides
Every model output goes through human review before production.
Evaluate before shipping
Every AI feature has an evaluation set and a quality threshold.
05
Security
Least privilege
Every service and person gets only the permissions they need.
Secrets out of the code
Credentials live in the secrets manager, never in the repository.
06
Operations
Every deploy is reversible
If it can't be rolled back in minutes, it doesn't ship.
Incidents leave lessons
Every incident ends in a blameless postmortem.
See them in practice.
Engineering notes show how these criteria are used — and broken — day to day.