Colophon

The publication system should earn its machinery.

Ordivon Web is the editorial and evidence-navigation layer around independent projects. It can become sophisticated without claiming ownership of the facts it presents—or carrying a server runtime it does not need.

FrameworkNext.js App Router + React
WritingComposable MDX + metadata-derived topic index
DeliveryStatic export via GitHub Pages
VerificationTypeScript, ESLint, static-export Chromium smoke, focused axe checks
RecoveryGit history + redeploy
StateStructured content at build time; no application backend

Publishing contract

Orientation here. Current truth at the source.

Project pages state the question, ownership boundary, current evidence, and next uncertainty. Articles preserve dated interpretation. Repositories, tests, receipts, and operational state remain canonical.

Every public route is generated at build time and published through GitHub Pages. Cloudflare remains authoritative DNS only. Historical routes are materialized as static redirect documents, so the public site needs no database, ISR layer, Worker, or request-time application module.

The repository keeps only checks that protect visible routes, content composition, and basic accessibility. Deployment recovery is a Git revert and redeploy, not a parallel evidence system.