The homepage of ComputeDriven, a systems studio.
One static page, no build step, no npm. index.html carries its own CSS and a little vanilla JavaScript; img/ holds the screenshots. The portfolio nav is loaded from /amp-nav.js, which is deployed by sync-nav.sh in the [&] workspace rather than edited here.
It has exactly one third-party runtime dependency, and it is worth naming rather than burying: the contact form posts to Formspree. Nothing else on the page calls out at load, and the page still renders and downloads work with formspree.io blocked — only the form stops.
Data driven keeps the result. Compute driven ships the derivation.
A claim is compute driven when the artifact carries enough — canonical input, executable semantics, a derived identity and its provenance — for an independent machine to derive the claim again.
Re-derivation proves fidelity, not correctness. A wrong computation re-runs perfectly and is still wrong.
The first proof object is T&R, a FreeBSD 15 distribution assembled from pkgbase. Images are published as GitHub releases on that repo; this page links to them directly and quotes their sha256 sums.
The #join section exists because the portfolio nav's CTA reads "Join ComputeDriven" and there was nothing here to join. What it offers is not a mailing list. The page's last admitted gap — every measurement was taken on our machines — is the one gap we cannot close ourselves, so joining is defined as supplying the missing thing: a second machine.
Reports arrive as GitHub issues on travel-and-rrabbit, filed through .github/ISSUE_TEMPLATE/boot-report.yml in that repo.
The two counts in `.jn-count` are hand-maintained. Nothing on this page fetches at runtime, so Reports received and From real hardware are stale by construction. Change them in the same commit that changes the date beneath them, and count only what is actually filed — a page that inflates its own evidence count has lost the whole argument. When the first report from real hardware lands, the "Never booted on real hardware" gap card must change too.
Under the boot-report grid, posting to https://formspree.io/f/xaewoadr. No email address appears anywhere on this page — that is the point of using an endpoint, so do not reintroduce a mailto: as a "fallback".
It is a real <form> with action and method, so it works with scripting off; the script only upgrades it to an inline reply instead of a redirect to Formspree's own thank-you page. _gotcha is Formspree's honeypot and is positioned off-screen rather than display: none.
"Sent" is printed only on an actual 2xx from the endpoint. A form that thanks you on submit and drops the message is precisely the failure this site is about. Failures print the reason the endpoint gave, and the typed message survives so it can be retried. If you touch that handler, keep the three paths honest: server error, network failure, success.
Every status on the page is measured, sourced, or marked not built. If you change a number, change the measurement record under it in the same commit — including the date and the machine. If a claim gets weaker, say so; the "Untested & unfinished" section is a feature, not a backlog.