Resources / Generated Derivatives

Generated Derivatives

Generated derivatives help readers inspect the project. They do not replace registered sources, registries, or governed control records.

Read derivative classes Retrieval layers Resources

Generated derivatives help readers inspect outputs, but source records remain the authority for underlying claims.

A generated page can be useful and still be noncanonical. Treat it as a reading layer with a source-basis trail, not as a claim owner.

Static diagram

Keep generated derivatives downstream from source and manifests.

The publication-provenance diagram shows source basis, route maps, page provenance, source manifests, asset manifests, static build output, and conflict paths back to source.

Diagram showing source basis feeding page route map, page provenance, source manifest, asset manifest, static build, internal reader routes, provenance links, and a publication-is-not-source-truth boundary. — The diagram illustrates the publication provenance system across source basis, route maps, page provenance, source manifests, asset manifests, static build output, and reader routes.

Derivative classes

Generated surfaces are reader aids with explicit limits.

The status label tells the reader what kind of inspection the surface supports before the page offers source or provenance links.

Class	Examples	Safe use	Limit
GitHub-facing Markdown	Repository-browser explainers generated from source-backed publication work.	Use as seed reading and orientation when the source hierarchy is preserved.	A generated explainer can guide reading, but public claims still require source-basis verification.
Tracked HTML explainer	No-network human-readable HTML outputs and prior explainer pages.	Use as a design and content prior for public pages.	HTML output remains a generated derivative, not independent authority.
PDF and document derivative	Generated PDFs, website copies, and document-library downloads.	Use for inspection and reading when the source path and status label remain visible.	Generated documents do not promote source claims or close physics gates.
Wiki and object browser	Generated wiki pages, relationship views, and browsable project maps.	Use for discovery, object browsing, and candidate source location.	When source and derivative disagree, inspect the canonical source and current tracked control record.
Public diagram or asset	Comprehension diagrams, route figures, and public manifest assets.	Use to improve comprehension of an already source-bounded page.	A visual aid is not source proof, registry proof, or publication acceptance.

Conflict handling

Derivative disagreement sends the reader upstream.

The derivative page is most valuable when it makes the audit path explicit and keeps the source owner visible.

Step	Action	Result
Read the derivative label	Identify whether the surface is generated Markdown, HTML, PDF, wiki, diagram, or asset.	The reader sees derivative status before trusting the surface.
Find the source basis	Use route provenance, source manifests, registries, or publication briefs to locate the owner.	The derivative becomes a path to source inspection, not a substitute for it.
Inspect the owner	Check the canonical source, source spec, registry row, handoff, or control record that owns the claim.	Claim language follows the owner, not the polished derivative.
Record the limit	State what the derivative helps readers do and what it cannot prove.	Generated derivatives help readers inspect the project, but registered sources and tracked control records remain authoritative.