This site, and how its figures are checked
Every figure on this site comes from one ledger with a source and a date. The build fails when a reference does not check out.
Buildingchecked 21/10
- Client
- Own project
- Role
- Designed and built it
- Period
- 10/2026 →
- Proof
- 1 claim
- Stack
- Next.js · React · TypeScript · Tailwind CSS · Playwright · Zod
- 1ProblemPortfolios state numbers nobody can check.
- 2BuildA typed claims ledger, evidence with access levels, copy linted for machine-sounding phrases.
- 3ResultThe CV PDFs and the site read from the same file.
Problem
Most portfolios state numbers that nobody can check, and a recruiter has no time to ask where they came from.
Build
Every figure lives in one ledger with its source, its date and how it was measured. The build fails when a number in the text is not stated by a claim it marks, when a reference breaks, when a private client's real name appears anywhere, or when a figure is past its re-check date.
The copy goes through a lint for phrases that read as machine written, built on my own editing rules. Fonts are self-hosted, there are no cookies or trackers, and motion is kept small and switches off when your system asks for reduced motion.
Result
The CV PDFs, this site and the LinkedIn text come from the same files, so they cannot disagree. The proof row on the home page, 1,338 test cases in 8 repositories where I wrote most of the commits, is computed from that ledger P1.
Limits
Status checks run from the server at most every half hour, so a short outage can be missed. Evidence marked on request is not public; ask and I will show it with client details removed.
My part
Designed and built alone, with AI coding assistants; every change is tested and reviewed by me.
Proof of delivery · NLV-26-POD
| # | Claim | Evidence | As of | Confidence |
|---|---|---|---|---|
| P1 | 1,338 automated test cases in 8 repositories where I wrote at least three quarters of the commits. |
| 21 Oct 2026 | I hold the artifact |