How this is built

Colophon

The site argues that a claim is worth more once you can check it. The fair test is whether that holds for the site itself.

What this is built with

Astro compiles markdown content and a JSON evidence corpus into a static site. There is no server rendering pages at request time and no client-side framework, so every page here loads and reads with zero client JavaScript. The two small scripts that do run are a light/dark theme toggle and a table-of-contents collapse on narrow screens; both are cosmetic, and neither is required to read a word of it.

The case studies, the capability map, and the fit page all render from one evidence corpus (src/data/evidence.json): one record per claim, each carrying a status (measured, designed-ceiling, verified, resume, david-supplied, assumption, or unverified) and a source, so nothing drifts between surfaces.

The gates the build enforces

A claim linter runs before every build and fails it if an evidence record is missing a required field, a designed-ceiling figure has no boundary note explaining why the ceiling was not reached, an em dash appears anywhere in the content or the corpus, or a case study cites an evidence id that does not resolve. A separate SEO gate checks the built HTML for a single <h1> per page, a canonical link, a title under 60 characters, and a description within a fixed length range, and fails the build on any of those too. Both gates ran on this page and on the changelog the same way they run on everything else here.

What AI wrote, what David verified

The scaffolding, the component code, and the first draft of nearly everything on this site, including this page, come from an AI coding agent working from a written specification. David owns the facts, the architecture decisions, and every number: he reviews each change and holds the commit and the deploy himself, so nothing an agent drafts reaches the live site without that review.

How to inspect it

The source is this website’s own repository: the markdown content, the evidence corpus, and the two build gates described above all live in the same place a reader could check them. There is no separate audit trail to request; reading the files is the audit.

Disclosures

This site carries no advertising, and no analytics or tracking script runs in your browser: view the page source and there is nothing to find. Page-view counts are pulled from server-side request logs, not a client-side script.