How the catalog is built

A reviewed source snapshot

The source manifest pins twelve public repositories to exact Git revisions, spec-spine 0.28.0 and an observation date of October 3, 2026. A routine build does not follow moving branches. Updating the snapshot is a reviewed source change.

Supported producer reads

The exporter verifies public visibility, checks each pinned corpus for freshness, and uses spec-spine config, registry list, show and relationships commands. It validates and deterministically sorts a website-owned presentation payload. It never parses managed registry shards directly.

Missing required sources, stale corpus data, unsupported producer requirements, schema errors or missing relationship targets fail the export. Prerendering fails without required catalog data and checks the complete route set.

What is exported, and what is not

The catalog contains declared lifecycle and implementation, summaries, ownership claims, relationships, source headings, frozen anchors, content hashes and pinned public markdown links. Released spec-spine 0.28.0 has no selected-content command. Full sections are available through the linked source, not reconstructed from derived files.

Verification and qualification are unknown in this export. Observation dates describe the snapshot rather than a claim of current branch state.

The publication boundary

The public build has no access to the private platform corpus. Any future platform summary needs an owner-approved selected publication contract before the website may consume it. Local evidence, handoffs, secrets and private infrastructure material are excluded from the static artifact.

There are no analytics, third-party scripts or remote fonts. Theme preference is saved locally in your browser.