Reader pathways · updated 6 August 2026
Book and Companion Experiences
A companion app, tool, or resource can help readers act on a work—but it should be a useful extension of the book, not a vague funnel or a way to collect more reader data than the experience needs.
Link a reader to the next useful action
A chapter-end link, QR code, or deep link should lead to a specific, relevant experience. Explain what the destination does, whether it is optional, what data it processes, and whether it is operated by the publisher or another party.
Keep the book and the tool distinct
The book’s arguments, the tool’s functions, and any claims about outcomes should be documented separately. A companion experience can operationalize a concept without implying that the book is software, that software validates the book, or that readers must use it.
Design for consent and continuity
Use privacy-preserving links where possible, do not embed credentials in print or public URLs, and provide an understandable fallback if a companion product changes or is retired. The public Context Pack can identify approved public destinations without disclosing protected material.
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
- Privacy and Access Boundaries
- Context Packs
- MCP and Interactive Books: Intended Direction
- Machine-Readable Publishing
For a concrete public record, inspect the metadata-only Context Pack demo. It remains separate from protected manuscript content and private editorial systems.