The project6 min read
Skills and evidence
The skills I claim in full-stack development, architecture, security, UX and quality. Each one has its evidence, read from the repository at build time: code, a test, a diagram or a decision.
Calling software “secure”, “tested” or “well architected” costs nothing. So for each skill, I show what you can check it with: the code that applies it, the test that proves it, the diagram generated from the source, the decision that explains it, and figures counted in the repository.
- test suites run against a real Postgres database
- 111
- apps/*/test/db/*.db.test.ts
- regression tests, most of which read the source code and reject any departure from a rule
- 92
- apps/*/test/*.regression.test.ts
- hand-written CHECK constraints, re-read on the database after every applied migration
- 169
- apps/erp/scripts/constants/db-invariants.ts#EXPECTED_CHECKS
- tables, out of the 54 in the schema, the public storefront can write to
- 6
- apps/site/scripts/lib/database-grants.ts#SITE_TABLE_GRANTS
- code files still copied from one application to the other, a list that can only shrink
- 28
- scripts/twins.manifest.json
- architecture decisions recorded as ADRs
- 14
- apps/docs/content/docs/(public)/architecture/decisions
Metrics covers what the project measures (performance, Core Web Vitals, tests, reliability, maintainability), what it doesn’t measure yet, and the protocol to measure it.
AI as leverage, engineering as the standard. In My contribution and AI, I go through how I build with Claude Code and what I keep in hand (design, trade-offs, development, validation), with the records behind it.
What I claim, and what proves it
How to read these pages
Nobody copies an excerpt by hand. Each one is read from the repository when the docs are built. Its caption gives the file, the quoted element and its line numbers in the file. For an SQL definition, you see the latest one a migration created.
If a function, a test or an SQL definition disappears or gets renamed, the docs build breaks, and the error message says what’s missing. So a piece of evidence can’t stay online without the code it quotes. The build reruns as soon as a quoted file changes (apps/docs/scripts/ignore-build.sh).
The figures aren’t typed by hand either. Each metric says what it counts and where.
The repository is private, so the public evidence is the excerpts. If you have access to the repository, you can replay everything:
| What can be replayed | Command |
|---|---|
| Both applications, with no copied code | pnpm check:twins, from the root |
| The tests that read the ERP’s code | pnpm exec vitest run test/ regression, from apps/erp |
| The ERP’s Postgres suite | DB_BEHAVIOUR_TESTS=1 pnpm test:db, from apps/erp, on a migrated local database |
| The guarantees of a migrated database | pnpm db:invariants, from the root, with DATABASE_URL set |
What these pages don’t prove
The docs build checks that the quoted code and tests exist, but it doesn’t run them. What runs in the pre-push hook is the tests that read the code, the tests for the files a change touches and, when the change calls for it, the Postgres suite. The end-to-end tests are run by hand (Quality). Quality and delivery says what this gate doesn’t cover, and the Architecture decisions explain the accepted trade-offs.
- Full-stackFeatures that go from the database to the screen, in two applications: a rule written once, a payment that matches the page, stock that doesn’t sell twice, a cache that follows the ERP.
- ArchitectureTools keep the code’s boundaries in place, without relying on discipline: one-way dependencies, two applications that no longer drift apart, a shared contract, decisions written down.
- SecurityGuarantees that don’t depend on the code they protect: a database that limits what the storefront can do, server actions that all open with their guard, signed messages, an assistant that can’t make up a number.
- UXThe UX rules are written into the code: pages that don’t wait for their slowest query, no toast for a success you can already see, actions you can undo, nothing lost, a storefront you can browse with the keyboard.
- QualityEach guarantee is proven where it applies: on a real Postgres database, with tests that read the code, with a hash chain the daily check recomputes, and with a gate that checks every commit before production.
- MetricsWhat the project measures in performance, Core Web Vitals, testing, reliability, quality and maintainability: the figures counted at build time, the thresholds that make a script fail, the dated readings, and a reproducible protocol for what isn’t measured yet.