Under the hood

How it’s built.

The same four steps, seen from the engineering side. Every project is built on these four rules, whatever its size.

Back to how it goes

1.0

Every piece of data has an owner.

Who may see what, what runs on a schedule and what each plan includes are rules in the database itself, not a checklist someone has to remember.

Postgres · row-level security on all 60 tables · pg_cron · plan gating at the query layer

2.0

It looks like one company built it.

One set of design decisions, made once and kept: type, colour, spacing and components shared everywhere.

design tokens · one type scale · 137 lines of duplicated header markup → one component

3.0

The data outlives the screen.

Screens get redesigned; the records under them have to stay right for years. Legal wording is stored once and checked on every build.

schema-first · protected-text registry · source-fidelity CI gate · forward-only migrations

4.0

Shipped means verified.

Nothing counts as live until my copy, the repository and the running site agree on the exact same version.

git rev-parse HEAD = origin/main = vercel --prod · append-only history