How this site is built.

Stack

Plain HTML, served as static files from Cloudflare’s edge. There is no CMS, no database, no server-side rendering and no client-side framework. No JavaScript runs on this site at all, which is why nothing here degrades when a script fails to load: there is nothing to fail. There is exactly one <script> element per page and it is a block of JSON-LD, which is data a search engine reads and a browser never executes. The build refuses any other spelling, and the site’s own Content-Security-Policy sends script-src 'none', so the claim is enforced by the server rather than by this paragraph.

The pages are generated from one layout, one fragment per page and a handful of shared partials, by a build script with no dependencies. The stylesheet and the self-hosted Geist fonts came out of the design source and are carried over unchanged.

Disclosure widgets, the mobile menu, the FAQ answers and the diagram descriptions are all the browser’s own <details> element. Everything that would normally be a small piece of JavaScript is either a native element or is not there.

Why not the framework it was designed in

This design was produced as a Next.js app on a beta runtime. Nothing on any page has state, a form or a server call, so the framework was doing no work that a static file could not do, and a beta runtime under a public address is a moving part with nothing to show for itself. It was dropped and the markup, the compiled stylesheet and the fonts were kept.

What you can check without taking my word for it

• View source on any page. The whole page is there. Nothing is assembled in the browser.
• Open the network panel and reload. Every request goes to this origin. No font provider, no analytics endpoint, no third-party request of any kind.
• Look for a consent banner. There is none, because there is nothing to consent to: no cookie is set and nothing is written to your device.
• Tab through a page with the keyboard. Every link takes focus in the order it appears and shows a visible focus ring. There is a skip link as the first stop.
• Turn on reduce motion in your operating system and reload. Every animation on the site stops.

The site is served from a content delivery network, which is what “Cloudflare’s edge” means, and that is a first-party arrangement rather than a third party the page reaches out to. The claim above is that your browser makes no request to anybody else, and that is the one you can check in the network panel.

What runs before anything ships

The build fails on a page with no title or description, and on a broken internal link: every href pointing into the site is compared against the routes the build just emitted. It fails on a template placeholder that reached the output unsubstituted, which is a real outage this site had, and on an unclosed conditional block.

It also fails on a claim with no evidence. Every capability term and technology name rendered as a badge on this site is checked against a file that records where that claim was published and what sentence it rests on. A term with no row does not ship, so adding a fashionable word to this site breaks the build rather than passing a review.

Those are small checks. They are the ones that would actually have caught something, because the failures they prevent are the ones a person reading HTML does not see.

Ownership

The domain, the hosting and the repository are in the owner’s accounts. Nothing here depends on a retainer to keep running.