Engineering

The rules are written down, every change is held to them and the build enforces them, which is where the consistency comes from.

Most codebases keep their conventions in people's heads. This one has a rulebook, and 623 architecture tests hold every change to it.

The rulebook, rule by rule →
In this section

How we build

AI writes most of the code, but it doesn't decide what to build, and it doesn't decide when something is ready to ship.

Context

Every concept, decision and plan is written down first, so the AI reads why something is done as well as what.

Proven core

What you'd be taking on if you built your own from scratch, and why we think you shouldn't.

Engineering standards

A written rulebook, enforced by the build, that keeps the code consistent, configuration-first and inside its boundaries, and that is yours to change.

Skills and AI

The code is half of what you receive, and the other half is how to change it.

Gates and tests

The suites and the rules, counted from the repository on every deploy.

Security

Single sign-on, deny-by-default permissions, passkey-signed approvals and a weekly bill of materials.

Platform

For the team that has to run it, and has probably been burnt by a platform choice before.