How it works
What happens between your chapter and your two files
No part of this is magic, and no part of it is yours to maintain. Here is the whole path, in order.
- 01
You write, in a browser
A block editor with the constructs a technical book actually needs: headings, figures with captions, tables, code with syntax highlighting, footnotes, callouts and cross-references. Beside it, an image library, an importer for the Markdown you already have, and a settings page generated from the book’s own schema. Nothing you type is markup you have to get right.
- 02
It becomes a document model, not a file
Every block is validated against a shared schema before it goes anywhere. This is the security boundary of the whole product: what you write is data all the way through, and never becomes something that runs.
- 03
The prose is reviewed
Before a page is set, the words are read: the platform’s rules for the book’s language, a spelling check, and the terminology sheet you keep for this book — the form it writes, and the forms to flag. Findings are ranked, and a gate you set withholds the downloads while a must-fix remains.
- 04
Typst composes it — twice
The first pass finds out where everything lands. The second uses that knowledge, so running heads, cross-references and the analytic index — built from the terms you marked while writing — carry page numbers that are true. Courtesy blanks get counted and reported rather than printed.
- 05
pandoc builds the EPUB, epubcheck judges it
The ebook is produced from the same document model as the print file, then validated in the same job that made it. The result is recorded, pass or fail, before anything is offered to you.
- 06
You get two files and a report
A 6×9 PDF, an EPUB, and a report naming the page count, the courtesy blanks, the timings and the exact version of every tool that touched the book.
Where the render runs
Composition happens in a container with no network access, a read-only root filesystem and no privileges, destroyed when the job ends. Your manuscript is never on a machine that could reach the internet on its behalf.
Pinned, so a book renders the same in six months
- Typst 0.15.1
- pandoc 3.10.2
- epubcheck 5.2.1
Your agent, if you want one
Any tool that speaks MCP can read a book, write into it and build it, with a token you mint. A book is closed to agents until you open it in its settings, read-only or read-write, and every change an agent makes is in the history. The platform runs no model and holds no key.
That is the whole pipeline. Put your name down and you will hear when it opens.