01
Write the brief
The brief names audience, reader job, source basis, acceptance criteria, and forbidden implications.
Operations explainer
The publication process exists because a mechanically valid page can still be weak. It preserves source basis, authority boundary, readability, visual evidence, and review evidence.
Publication comprehension
The publication process begins with a brief and source spec, then produces a page, screenshots, review evidence, provenance, and manifest updates.

The diagram is a static reader aid. It does not replace the source files, route dossiers, or claim-status records that govern the topic.
Mechanism
01
The brief names audience, reader job, source basis, acceptance criteria, and forbidden implications.
02
The source basis controls what public copy may explain.
03
Screenshots and human review catch public-comprehension failures that commands cannot prove.
Terms
Boundaries
Safe reading
Related routes
Source basis
Source basis
Generated noncanonical upstream explainer: github-facing/documentation-curator-publication-process-explainer.md.
Publication lifecycle
The brief defines reader, reader job, source basis, narrative shape, visual strategy, acceptance criteria, and forbidden patterns before public copy is produced.
Review boundary
Publication work can improve the reader journey, expose provenance, and record screenshots. It still remains downstream from the source basis.
Related reading
These links keep the primary reader journey inside the website. Source links remain visible in the provenance section.
Source provenance
The links below point to reviewed upstream source surfaces. This website adaptation remains downstream from those sources and from the registered authority records they cite.
Reviewed generated noncanonical upstream source for this page.
Inspect sourceCommitted control source for brief-first publication discipline.
Inspect sourceCommitted script source for mechanical publication-process checks.
Inspect source