Public documentation · updated August 2026
Accountable publishing infrastructure.
Agentic Publishing documents the boundaries around source-aware publishing: what a record says, who approves it, what is public, and what remains private. It does not promise autonomous factual publishing.
Shared language
Agentic Publishing Glossary
A plain-language glossary connecting editorial publishing work with the engineering terms used to build accountable publishing systems.
Structured production
Manuscripts as Code
A practical model for version-controlled manuscript sources, editorial review, validation, and repeatable publishing outputs.
Discovery and validation
Machine-Readable Publishing
Practical guidance for valid structured data, crawlable public pages, sitemaps, llms.txt, and transparent limits on discovery signals.
Reader pathways
Book and Companion Experiences
How a book can point readers to a companion tool or experience while keeping the relationship useful, honest, and privacy-aware.
Getting started
Start Here: Publishers and Developers
A practical first path for publishers and developers adopting accountable, source-aware publishing infrastructure.
Public context
Context Packs
How Context Packs define a versioned, bounded public description of a publishing work without exposing protected text.
Approved delivery
Release Manifests
How approved Release Manifests make public publishing releases versioned, bounded, and auditable.
Traceable inputs
Source and Provenance Records
How Agentic Publishing records identity, version, scope, provenance, and exclusions before public delivery.
Accountable publishing
Editorial Workflow
An accountable editorial workflow for source-aware publishing: research, drafting, verification, review, approval, and release.
Publication control
Release Gates
How approval gates separate draft records, approved source material, and published metadata-only releases.
Change accountability
Versioning and Change Records
How version identifiers and update policies make publishing records understandable, reproducible, and withdrawable.
Machine-readable delivery
Public JSON Endpoints
A guide to stable, metadata-only public JSON endpoints for approved publishing releases.
Data boundaries
Privacy and Access Boundaries
The public, private, and authorized-reader boundaries that protect manuscripts, customer data, credentials, and unpublished releases.
Product direction
MCP and Interactive Books: Intended Direction
The intended direction for authorized, source-aware interactive books and MCP-compatible tools, with clear limits on what is available today.
Read-only public demo
Inspect The Maha Principle Context Pack, its Context Pack JSON, and its demonstration Release Manifest. These public records contain descriptive metadata only—no book text, credentials, reader data, or private releases.