Shared language · updated 6 August 2026
Agentic Publishing Glossary
Authors, editors, and engineers do not need to use the same tools, but they do need a shared language for describing a traceable publishing system.
Manuscript as code
A manuscript can be kept in structured, portable source files such as Markdown rather than being defined by one proprietary editing surface. “As code” means its changes, inputs, and outputs can be made traceable; it does not mean every author must use Git or write software.
Compilation and release
A compilation step transforms approved source into a particular output: a PDF, ePub, web view, metadata record, or accessibility variant. A release is the editorial decision to make a specific approved output available. Compilation is not approval.
Prose linting and consistency checks
Automated checks can flag repeated phrases, missing metadata, inconsistent labels, or formatting problems. They are prompts for editorial review, not replacements for copyediting, fact checking, sensitivity review, or rights clearance.
Chunking, retrieval, and answer systems
Chunking divides authorized content into manageable units for retrieval. A vector store can help a system find relevant authorized material. It cannot itself establish truth, authorization, or a right to expose protected text.
This page develops ideas first discussed in the Agentic Publishing community. The documentation states the current public boundary and does not turn discussion or roadmap material into a product guarantee.
Related documentation
For a concrete public record, inspect the metadata-only Context Pack demo. It remains separate from protected manuscript content and private editorial systems.