This manual is published for machines as much as for people. An agent can fetch any page as plain text, ask where a rule lives, and load the whole corpus in one file sized to its budget.
| Address | What it is | When to read it |
| `https://vibevm.org/doc/llms.txt` | the index: one line per page, the page's first paragraph | first, to choose a page |
| `https://vibevm.org/doc/<package>/<version>/<page>.md` | one page as plain Markdown, block numbers included | to answer one question |
| `https://vibevm.org/doc/<package>/<version>/<page>.xml` | the same page in its source form, with every rule address and example intact | to quote a rule or run an example |
| `https://vibevm.org/doc/llms-small.txt`, `llms-medium.txt`, `llms-full.txt` | the corpus in three sizes, stable text first | only when a task spans many pages |
| `https://vibevm.org/doc/manifest.json` | every page with its language, audiences, status and anchors | to navigate programmatically |
| `https://vibevm.org/doc/resolve/?uri=spec://…` | the resolver: an address in, the page and block out | when a message or a page cites an address |
| `https://vibevm.org/doc/ru/…` | the same files for another language | when the user reads that language |
The site also serves the page manifest, a JSON list of every page with its statuses, languages, audiences and anchors, at `/doc/manifest.json`, and resolves a `spec://` address at `/doc/resolve/?uri=…`; `<package>` is the group and name of the manual, `org.vibevm.core/vibevm-docs`, and `<version>` is a number or `latest`.
The same pages live in the machine [store](../glossary/index.xml#store) once `vibe cache add org.vibevm.core/vibevm-docs` has run. `vibe explain "spec://org.vibevm.core/vibevm-docs/<page>#<anchor>"` prints a page or a block; `vibe doc manifest --llms small` prints the page list from the store. Nothing on this path contacts the network, which is why proprietary documentation is read this way.
Every block on a page carries a number, `p12` and so on, assigned when the page is built and the same in the web page, the Markdown and the XML. A citation is the page address plus that number: `spec://org.vibevm.core/vibevm-docs/model/boot-lane#p7`. Headings keep their named [anchors](../glossary/index.xml#anchor) as well, and a named anchor never changes once published; a [block number](../glossary/index.xml#block-number) names the current text and may shift after an edit, like a line number.
Rules on a page are quoted from the [specification](../glossary/index.xml#specification) by address and shown in the specification's own language. Prefer the address of the specification over the address of the manual when you tell a user what a rule says; prefer the manual's page when you explain why.
1. On an error, read the address the message names, then the page the diagnostics page maps it to.
2. On a question, answer from one page: the first paragraph is the plain answer, the rule blocks carry the exact wording.
3. On a task, take the page's request block as your task and substitute the user's names and paths. Run it, then run the asserts. The task is done when every assert exits zero.
4. When choosing among documentations of one package, prefer the one marked official and name the publisher of a community one.
5. Never load the full corpus when one page answers.
`vibe mcp serve` offers the same operations as tools. `explain` looks at one node of the map by address; `query` finds nodes, and the two are separate verbs on purpose. `select` takes up to seven predicates, `uri:`, `symbol:`, `kind:`, `scope:`, `has:`, `lacks:` and `depth:`, whitespace separated and joined by AND, with no operators. An unknown predicate, a repeated one or an empty query is an error that names the token and lists what was expected.
`query_package` returns the full lock entry of an installed package. `read_subskill` returns the content of an active [subskill](../glossary/index.xml#subskill) wherever it lives, in the project tree or in the machine store. `materialise_subskill` copies a lazily pulled subskill into the project tree and refuses to overwrite without `force`; it is the one tool that writes.
The language packages of the `mcp` kind bring servers of their own with four tools, `tcg_validate`, `tcg_scope`, `tcg_complete` and `tcg_type`: thin adapters over the operations of the same names. Each takes a required `language`, `typescript` or `rust`, and the operation's own parameters unchanged. Each answers with the enriched result as structured content plus a short text with the findings first.
Text written for agents is never part of a project's [boot lane](../glossary/index.xml#boot-lane); this manual is fetched when needed, not read at every session start.
The boot lane itself is pure file reading: nothing in it executes, and the manual is not on it.
A page that exists in the source language but not in the language you asked for is served in the source language under the address you asked for, with a note; do not treat it as missing.