The page inventory

This was the work plan. Every page of the tree is listed here with the path it got, the kind it is, the one line it had to answer, and where its facts came from - split into thirteen packages so that independent writers could each take one without touching the same file. Every page listed here exists today, so this document is kept as a record of how the tree was planned rather than as an open queue; Adding a page is what a genuinely new page follows now.

The decision#

The work is split into thirteen packages, each one a folder or a group of subfolders with no overlap. Two writers can take two packages at the same time without touching the same file. Every package can be finished on its own, because a page is written to stand alone and the index it belongs to is generated.

glossary.md is not a package: every writer adds the terms their pages use, in alphabetical order, at most two sentences each.

Why#

One folder per writer, because a folder is the unit that has no shared files. The index of a folder is generated, so two writers never edit the same index; the only shared file in the whole tree is glossary.md, and an entry there is one paragraph that can be added without reading the rest.

The reference before the guide and the how-to pages. A guide page links into language/, and a link that does not resolve is an error. Packages 2 to 9 have no dependency on anything but CONCEPT.md and std/, so they go first; 1, 10 and 12 come after them.

A page that has no source is not written. Every row below names where its facts come from. Where CONCEPT.md is silent or contradicts the compiler, the page says so and the contradiction goes into the report rather than being resolved by the writer.

The pages#

The columns are the path below docs/, the title, the kind, the one line the page answers, and the source field it carries. done in the last column means the page exists and passes the gate.

Package 1: guide#

The learning path, in order, mirroring examples/tour/src/*.trb. Every page has order and prerequisites. Since 2026-09-29 the guide opens with one tour, guide/tour.md, which replaced the sixty-second page below and a later 15-minute tour; guide/tests-and-tooling.md went into guide/installing-and-running.md and guide/modules-and-packages.md, and building the toolchain moved to contributing/building-from-source.md.

Package 2: syntax, values and types#

Package 3: functions#

Package 4: types#

Package 5: traits and generics#

Package 6: pattern matching and errors#

Package 7: collections, iteration, concurrency#

The three pages of concurrency-and-streams/ are status: planned until the runtime has them. A planned page carries the planned banner and is left out of the generated skill.

Package 8: modules, reflection, configuration, execution, extensibility#

Package 9: standard library#

One page per package of std/, each kind: package, each with the Declarations section between the generator markers so that milestone 8's torb doc can fill it.

Package 10: how-to#

Package 11: explanation#

Distilled from the Decision Log of CONCEPT.md. Each page takes one decision, gives the argument, and says what a reader has to do differently. These pages matter most for a model: a wrong mental model produces code that compiles and means something else.

Package 12: the contrast pages#

Four pages, each kind: contrast, each titled Coming from <language>. They are the highest-value pages for a model, because the failure is not ignorance but the habits of a language it does know.

Package 13: tooling#

torb doc is status: planned.

Consequences#

For a writer taking a package:

1. Read How to write here and the front matter first. They are short and they are the whole contract.
2. Copy a template from Add a page, and copy the tone from the page marked done in your package. A page written like page 4 is the goal; a page written in a new style is a defect even when it is correct.
3. Take every fact from the source column. Read the section of CONCEPT.md and the std/ file, and run the example through the toolchain. Never write a snippet from memory.
4. Create the folder's index.md together with your first page, with a ## What belongs here section that says what does not belong in it.
5. Add every term your pages use to the glossary, in alphabetical order, at most two sentences.
6. Run docs index and then docs check, both green, before you are done.
7. Report what you could not decide. Where CONCEPT.md is silent, ambiguous, or contradicted by the compiler, say so in your report instead of choosing. That list is more valuable than a page that guesses.

Related#

• Add a page - the steps and the templates.
• How to write here - the writing rules.
• The front matter - the nine fields.
• The docs commands - the gate.
• How this documentation is structured - the tree and the kinds.