The build pipeline

The build pipeline

One renderer, many publications. A single Astro pipeline reads an exact revision snapshot and emits an isolated static site per target.

const build = assemblePublication(target, revision);

We hold every claim to the same bar: it must be reproducible from an exact commit. The pipeline is no different. The pipeline reads a frozen revision set, renders each article through one Markdown policy, and emits an isolated static site — no runtime API, no credentials, no cookies. That constraint is not decoration; it is what makes the writing trustworthy. If a reader cannot rebuild the artifact behind a sentence, the sentence does not ship. The same discipline governs how we measure success: a small, closed set of privacy-minimal signals, never fingerprinting, never article-level PII. The result is a publication that behaves like the products it describes — deterministic, isolated, and honest about its own evidence.

We hold every claim to the same bar: it must be reproducible from an exact commit. Ownership is no different. The pipeline reads a frozen revision set, renders each article through one Markdown policy, and emits an isolated static site — no runtime API, no credentials, no cookies. That constraint is not decoration; it is what makes the writing trustworthy. If a reader cannot rebuild the artifact behind a sentence, the sentence does not ship. The same discipline governs how we measure success: a small, closed set of privacy-minimal signals, never fingerprinting, never article-level PII. The result is a publication that behaves like the products it describes — deterministic, isolated, and honest about its own evidence.