Operations explainer

Documentation Curator Publication Process

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 lifecycle
Visual orientation only: publication evidence improves readability without changing source authority.

Publication comprehension

Public readability is downstream from source binding.

The publication process begins with a brief and source spec, then produces a page, screenshots, review evidence, provenance, and manifest updates.

Diagram showing publication brief, source spec, reader page, screenshots, human review, manifests, and readable page is downstream.
Static comprehension diagram: publication improves explanation without changing source authority.Mermaid source: docs/content-dossiers/operations-publication-process/diagrams/publication-source-review-flow.mmd. Manifest id: comprehension_operations_publication_review_flow.

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

How to read this surface.

Terms

Define the loaded words before using them.

Publication brief
A planning surface for reader job, source basis, and acceptance criteria.Not source authority by itself.
Source spec
The source-boundary contract for a public page.Cannot strengthen source claims.
Human review
A reviewer judgment that the page teaches the topic without overclaiming.Separate from scripted PASS.

Boundaries

What this page must not imply.

No generated authority
Readable pages stay downstreamA polished public page cannot supersede its source files or registries.
No validator-only comprehension
Human review remains requiredScripts can catch missing structure, but not prove reader understanding.

Safe reading

A useful summary also names the unsafe one.

Safe summary
Supported readingPublication work translates source-bound material into readable pages with screenshots, human review, manifests, and provenance.
Unsafe summary
Forbidden shortcutA public page or screenshot changes source authority, proves comprehension by script alone, or promotes source claims.

Related routes

Source basis

Use these as provenance, not primary navigation.

Publication lifecycle

A page-specific brief controls the work.

The brief defines reader, reader job, source basis, narrative shape, visual strategy, acceptance criteria, and forbidden patterns before public copy is produced.

Brief
Define the reader jobThe brief names what the page must help readers understand and what it must not imply.
Source spec
Bind the source basisThe source spec preserves source materials, authority boundary, and core claims.
Page
Adapt for readersThe website may improve clarity and structure without changing the source claim status.
Review
Check rendered evidenceScreenshots and before/after review capture public readability beyond command success.

Review boundary

A readable page is not an authority upgrade.

Publication work can improve the reader journey, expose provenance, and record screenshots. It still remains downstream from the source basis.

Human
Review covers comprehensionScreenshots and review notes capture public readability risks that deterministic checks cannot fully decide.
Source
Claims remain boundA source spec prevents the page from silently strengthening mathematical, scientific, governance, or workflow claims.

Related reading

These links keep the primary reader journey inside the website. Source links remain visible in the provenance section.

Source provenance

Source links are for inspection, not primary navigation.

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.

Source authority