Resources / Publication Process

Publication Process

Publication turns source-bounded material into readable pages. It improves inspection and comprehension; it does not authorize source claims.

Read the chain Library Resources

Publication pages move from brief and source specification through review evidence and manifests before public routing.

Publication pages are reader surfaces, not source authority. They are useful when their source basis, validation limits, and review status stay visible.

Static diagram

Read publication as review flow, not authority promotion.

The publication flow diagram shows brief, source spec, reader page, screenshots, human review, manifests, and provenance in one auditable chain.

Diagram showing publication brief, source spec, reader page, screenshots, human review, and manifests. — The diagram illustrates publication review flow from brief and source specification through reader page, screenshots, human review, and manifests.

Source-to-publication chain

Each publication layer has a different job.

The chain keeps process metadata secondary to the reader topic while preserving enough provenance for review.

Layer	Function	Website use	Limit
Canonical source or registry	Source basis for claim-bearing material.	Verify public claims and authority class before writing or reusing copy.	Publication cannot promote a claim beyond this owner.
Markdown source spec	Publication source lane for an explainer.	Define purpose, audience, outputs, source materials, and claim boundary.	A source spec constrains the page; it does not strengthen upstream claims.
Publication brief	Reader-experience and quality contract.	Define reader job, document type, visual strategy, acceptance criteria, and forbidden patterns.	A brief shapes publication quality, not source authority.
GitHub-facing Markdown	Repository-browser and AI-reader derivative.	Reuse as seed copy when source hierarchy is preserved.	A generated explainer can guide reading, but public claims still require source-basis verification.
Tracked HTML explainer	No-network human reader derivative.	Reuse as design/content prior, not independent authority.	Tracked HTML remains downstream from source and publication records.
Website page	Integrated public reading surface.	Present subject-first content with provenance and internal navigation.	Publication pages are reader surfaces, not source authority.

Validation limits

Validation proves process conformance; it does not prove physics claims.

Positive publication evidence is useful because it is narrow. The route keeps those limits visible beside each signal.

Signal	Supports	Does not prove
Brief review	Reader job, visual strategy, forbidden patterns, and acceptance criteria.	The underlying scientific or workflow claim is true.
Source-spec parity	Shared source basis, authority boundary, and core claims.	Identical section order or stronger claim status.
Screenshot QA	Layout, legibility, visual framing, and responsive behavior.	Human comprehension by itself or source correctness.
Validator PASS	Process conformance, link integrity, manifest integrity, and build consistency.	Physics claims, publication acceptance, or upstream promotion.

Page-type library

Page type follows reader job, not repository convenience.

A publication page begins with what the reader needs to understand, then exposes provenance and source boundaries after the topic is clear.

Page type	Reader job	Useful pattern
Overview article	Orient readers to a domain before terms or process details dominate.	Subject-first summary, claim boundary, related internal routes.
Concept explainer	Make one idea understandable with definitions and examples.	Definition table, boundary map, provenance note.
Workflow guide	Explain a sequence without turning process evidence into authority.	Step table, safe/unsafe use, validation limits.
Reference catalogue	Let readers scan a set of materials with stable labels.	Status matrix, reader-job grouping, internal routes first.