The book
Book, Source and Map
The Context Book is the brain as people read it: one page per block, ordered by group. Book reads it, Source is the markdown behind a page, and Map draws the whole graph in 3D; all three show the same blocks.
The book is what you open in the browser. It is rendered from the same markdown an AI reads over MCP, so what you read and what your AI reads cannot drift apart.
Where things are
| Address | What it is |
|---|---|
/<organisation> | The organisation's book: the shared context, then each project as a chapter |
/<organisation>/<project>/book | A project's front page: what the project is, how many chapters are written per group, and the contents |
/<organisation>/<project>/book/<group>/<entity>/<block-key> | One page, for example …/book/users/persona/primary-persona |
/<organisation>/<project>/book/map | The Map |
/<organisation>/<project>/book/changes | What changed, for readers |
/<organisation>/<project>/book/llms.txt | The book's index for AI tools |
The book is for members of the organisation. Anyone else, signed in or not, gets the same not found a missing page gives.
Three views of the same context
The switch in the header offers three views. On a page, each keeps your place.
- Book reads the context. Each block type is drawn with its own template: a journey as a timeline, an architecture block as a diagram, a business model canvas in its nine boxes.
- Source is the markdown the graph stores, for people who may edit. It saves as you type and checks the version, so a change someone else made in the meantime is reported instead of overwritten. Source opens the block you are on.
- Map is the whole graph as a 3D cloud, drawn from the references and links between blocks. From a page it opens focused on that block (
?focus=<block-key>). On the map the book's menu selects instead of navigating: pick a group or an entity and the map shows it.
Messages on a page
Under every page people leave messages: a question, an objection, a note for whoever holds the block. Messages are part of the context. An AI reading the block with get_block gets the open messages with it, and so does the page's markdown twin.
The Design group is a brandbook
The Design group reads as five chapters: Foundations, Brand assets, Components, Guidelines and Applications, with a visual cover at /book/design. Each component page has an Anatomy & specs section: per part its purpose and the foundations it uses. The visual identity can carry a theme that dresses the Design pages in the project's own colours and type, refused when its contrast falls below WCAG AA.
Markdown twins and llms.txt
Every page also answers as markdown: add .md to its address and you get the body and its open messages as plain text. The project's llms.txt lists the written pages with links to those twins, so an AI tool that cannot use MCP can still read the book. Both follow the same rule as the book: members only.
Sharing one page
Anyone who can edit can give a single page a public link for someone outside the organisation: on the page, open Share › Share this page and switch on Share outside the organisation. An AI does the same with share_block, after asking you.
- Anyone holding the link reads the current version of the page, without an account. Search engines are asked not to index it. A member who opens the link is sent to the page in the book.
- There is one link per page; sharing again returns the same one. Switching it off makes the address stop working at once.
- Locked pages and legal pages are made public by owners and admins only. An archived page cannot be shared, and archiving a page ends its link.
- The book, the Source view and
get_blocksay Public link on a page that has one.
The organisation decides for all its pages, under Settings › Organisation › General › Public links (owners and admins): Allow public links switches every link off or on at once, A link works for sets a lifetime (until it is turned off, 30 days, 90 days or a year), and the list shows every live link, who made it and when, with Turn off per link and Turn all off. Every link made or ended writes a line in the activity log: who, when and why.
Next
- Writing a page: headings, tables, diagrams, charts and embeds.
- Relations: what the Map draws.
- Export: taking the whole book with you.
Last updated: