Provenance

The provenance of this site — what built it, what renders it, what versions exist, what guarantees they carry — is part of the site's load-bearing trust posture. This page documents the chain.

Authoring

This site is authored at /opt/hypo-site/ on the operator's local workstation (tradingstation, in Romania), under the version-control of a private git repository. The English source is hand-authored by the founder, in collaboration with an AI session that operates as the site's canonical steward per blueprint §13.1 of v1.2 onward. The AI session maintains coherence between this site, the bot blueprint (/opt/hypo-blueprint/BLUEPRINT.md), the monograph (/opt/hypo-blueprint/HYPO-MONOGRAPH.md), and the site's IA + content layer.

The locale translations of every page are generated at build time by Claude (claude-opus-4-7) using the translation pipeline documented at /opt/hypo-site/scripts/translate.ts. Translations are frozen per release and committed to the repository alongside the canonical English source. No translation is re-generated on-demand at runtime.

Build pipeline

The release procedure runs make publish on the site VPS (separate from the bot's VPS, per blueprint §8.2). The Makefile executes:

1. Pull the latest commit from the private git remote.
2. Install pinned dependency versions via pnpm.
3. Run the translation script for any en-source changes since the last release.
4. Run `NEXT_OUTPUT_EXPORT=1 next build` for static export.
5. Generate Open Graph card PNGs per locale × page.
6. Sign the canonical manifesto.txt with the Ed25519 release key.
7. Atomic symlink swap into the Nginx document root.

Each release writes a SHA-256 manifest of the output tree to /.well-known/release-manifest-vYYYY.MM.DD.sha256.txt. Any reader can compare the served HTML against the manifest entry to verify they are reading the released byte-stream.

Versioning

Site versions follow the vYYYY.MM.DD pattern, matching the bot's date-based versioning convention but with independent version numbers — the site's version moves only when the site changes, not when the bot's parameters evolve.

Each version is a git tag (site-vYYYY.MM.DD). Each tag is built reproducibly: cloning the repo at the tag, installing pinned dependencies, running make publish produces byte-identical output to the original release. The reproducibility procedure is documented in detail at /colophon/proof.

The site's current version is displayed in the footer and in the citation block on every page. The current version stamp is the load-bearing identifier — any claim about the site's content is implicitly relative to the version.

Render pipeline

Next.js 16 with the App Router. Static export at build time. MDX content with co-located TSX page wrappers. CSS via vanilla CSS-in-JS for the design system, with the palette tokens defined in app/globals.css and the component library in components/.

Self-hosted fonts:

No webfont CDN. No analytics. No third-party JavaScript. The site runs as static HTML served by Nginx behind a per-subdomain Let's Encrypt certificate (HTTP-01 challenge, no wildcard).

Hosting

The site VPS is a sovereign-operated host distinct from the bot's VPS. The hosting provider is selected by the Foundation; the choice is not published because hosting provenance is not part of the site's identity claim (any equivalently-capable host could serve the same files; the cryptographic verification anchors the trust independent of hosting).

DNS for hypo.markets is managed at the registrar level by the operator. The registrar is selected by the Foundation; the registrar's identity is not material to the site's trust (the registrar can fail; the cryptographic signature on the manifesto survives the registrar). DNSSEC is currently not enabled (see the explicit-deferral ledger in blueprint §11.9 of v1.2).

Per blueprint §11.6, mirrors are permitted for any purpose with attribution. A mirror serving the same byte-identical signed content is operationally equivalent to the canonical site; the cryptographic anchor in /colophon/proof lets readers verify.

Change-log

Every release records a delta entry at /colophon/changelog describing what changed since the previous release. The changelog is the human-readable trail; the git tags are the machine-readable trail. The two should agree.

Author attribution

Content authorship is collaborative between the founder and the AI steward. Per blueprint §13.1, the AI session is canonical steward of content, IA, implementations, and menus. The voice on the site is HYPO's; the steward's role is to maintain the voice's coherence across versions.

Attribution to specific contributors is not provided. The site's content is the Foundation's work as an institution; the Foundation does not split credit. The site's citation block names the publisher (Aurelius Foundation) and the author (HYPO) and does not enumerate the human and AI contributors. Attribution at this granularity is, in the Foundation's view, ceremonial rather than informational.

If you want to verify a specific claim about the site's provenance — that a given version produces a given hash, that the manifesto on a mirror matches the canonical signature, that a translation was generated at a given date — the cryptographic anchors and the reproducibility procedure at /colophon/proof are the canonical surfaces for the verification.