01
Declare the route
A route-map row states what a public page adapts and which boundary type applies before provenance is generated.
Source authority / PG-024
Publication And Provenance System
The website publishes static pages and public assets through manifests, hashes, and validation gates. Those records make publication auditable. They do not make the website a source of scientific truth.
Why provenance exists
Publication needs audit evidence, not authority inflation.
A static page can drift, a public asset can be regenerated, and a source dependency can change. The provenance system records enough structure to inspect those changes while preserving the rule that upstream sources and governed records own project claims.
02
Hash the page and sources
Page provenance records the local page hash and source hashes where source files are available to the generator.
03
Register public assets
Source-manifest rows state source path, approval status, claim status, and notes for public diagrams, PDFs, TeX files, and other files.
04
Verify served bytes
Asset-manifest validation checks that published files exist and that byte counts and hashes match the manifest.
05
Keep reader routes internal-first
When an internal route exists, primary reading stays on the website while source and manifest links remain provenance.
Manifest roles
Each manifest answers a different audit question.
The manifests are not interchangeable. One declares route intent, one records page provenance, one records asset source/status metadata, and one verifies the files served from the public build.
- Route map
- page_route_map.jsonDeclares each public route, its local page source, source basis, publication status, and boundary type.
- Page provenance
- page_provenance.jsonRecords generated page hashes, source dependency hashes where available, commit metadata, and provenance URLs.
- Source manifest
- source_manifest.jsonRecords public asset source paths, approval status, notes, and asset-level claim-status boundaries.
- Asset manifest
- asset_manifest.jsonIndexes served public files with byte counts, hashes, kinds, titles, and source-manifest references.
Hash boundaries
Hashes identify state; they do not certify meaning.
The useful question is narrow: did this page, dependency, or asset match the recorded bytes? The stronger question, whether the page is conceptually complete or a claim is true, remains outside hash authority.
- Page hash
- Identifies rendered source stateUseful for detecting page drift. It does not prove that the explanation is complete or conceptually correct.
- Source hash
- Identifies a dependency versionUseful for source audit. It does not promote a claim, resolve a gate, or replace source review.
- Asset hash
- Identifies served bytesUseful for verifying that a file matches the manifest. It does not make a diagram, PDF, or image authoritative.
- Validator pass
- Confirms a bounded checkUseful as build evidence. It does not become scientific proof, release approval, or human review.
Internal-first routing
Primary reading stays on reviewed internal routes.
Internal-first routing is a readability rule. It keeps readers on curated website explanations when those routes exist, while keeping manifest and source links visible as provenance for inspection.
Source Authority
Read the broader trust boundary for website pages, generated derivatives, and upstream records.
Open routePublication process
Review the maintainer workflow for briefs, source specs, screenshots, human review, and manifest updates.
Open routeResources
Inspect the public resource index that links manifests, ontology documents, diagrams, and downloads.
Open routeOntology Documents
See how registered TeX source and generated PDF derivatives are presented with explicit boundaries.
Open routeDiagram Gallery
Inspect website-local visual aids with source paths, captions, and non-authority status.
Open routeSafe reading
A useful summary names the forbidden shortcut.
- Safe summary
- Auditable publication statePublication provenance records which routes, sources, manifests, and public assets were checked for a static website state.
- Unsafe summary
- Manifest equals truthA route-map row, page hash, source hash, asset hash, or internal-first link proves a scientific claim, grants release approval, or replaces source authority.
Source provenance
Use source links for audit, not as the primary reading path.
The links below expose implementation evidence for maintainers. Public reading should start with the internal routes above, then inspect these files when an audit trail is needed.
Website architecture note
Maintainer-facing architecture source for route families, publication surfaces, manifests, and validation gates.
Inspect sourcePage provenance generator
Script that builds page provenance from the route map and available source state.
Inspect sourcePage provenance validator
Script that validates route coverage, page hashes, source dependency records, and path safety.
Inspect sourceManifest path validator
Script that validates source-manifest and asset-manifest file existence, hashes, and source references.
Inspect source