Docs

Last updated: 8 September 2026

Read it in this order

The first five pages are written to be read in order, and together they take about an hour and forty minutes. The four after them are for looking things up, and nobody is expected to read a reference through. The time beside each page is its word count, with the code plates left out, at two hundred words a minute: 2 September 2026 for the pages that were here then, 8 September for Citing What You Read. It is an estimate of reading, not a measurement of anything.

That list is a navigation landmark, and a skip link stands before the band on every page, so a keyboard reaches the text without walking through the doors first. Every page of the docs carries its Previous and its Next, where they exist, in the line at its foot, with a link back to this page, and the Docs door in the band wears the current mark on every page behind it: a door says where you are while you are in any room behind it.

Benchmarks is not a door. The band holds two, Docs and Writing, and a third would not fit beside the wordmark and the lamp on a narrow screen. Benchmarks is reached from the list above and from the address line at the foot of every page of the docs and of the front page.

What every page keeps

The library comes first and the term second, in that order inside the sentence. A note is a book. The Search for line under its title is the label, written by a person to say what questions the book answers. The router is the catalogue. Vesta is the librarian, and when the library has nothing for a question she says so in its own words: I do not have that book. The technical noun follows as the explanation, keyword index, full text search, roster, and never leads.

Every number carries its platform, its corpus, its commit and its date in the sentence that quotes it, because a number that cannot say where it came from is marketing. Some figures were measured on the private fleet the authors run, against an answer key the repository ignores; those are labelled as figures a reader cannot reproduce, and the demo eval that ships with the source is the reproducible half. No test count is printed anywhere, because more than one session writes the repository and the count moves between them.

The demo fleet is invented. zed is a software architect, steve a marketing analyst and yaron a nutrition assistant, three tiny agents with an answer key, and every path a reader is asked to follow in these docs uses them. The fleet the authors run is private, which is the product working as designed.

The source is public at github.com/richard-wollyce/ulpia, under Apache 2.0, with LICENSE and NOTICE at the root. Where a page quotes a file, it links that file in the repository, so a sentence here can be checked against the line it came from. What no page does is promise a feature the repository does not hold.

Every terminal plate that shows a run captions the date and the commit of that run, so a plate that has gone stale goes stale visibly instead of quietly. A plate that shows a documented shape rather than a pasted run says so in its caption.

Where it stands, part by part

Early, used daily, and honest about which is which. The items that are not built each point at their line on What Is Next, where the trigger that would build them is named.

tools/kb
Works, and is used daily. cargo test in tools/kb is green, and the count is left out on purpose, because more than one session writes the repository and the number moves between them. One dependency.
kb ui
The reading room. It binds 127.0.0.1 and nothing else, and there is no flag to bind anywhere else, because the page has no business leaving the machine.
The site
A static front on Cloudflare Pages, with one Rust binary behind it that is not in the production path today; it serves the site locally and stands up on a subdomain the day something has to be computed per request.
Local model routing
Not built. Its line is under the work in front of us on What Is Next.
Voice
Not built. Its line is under kept possible, not built on What Is Next.
A macOS binary
Published since kb-v0.2.2, as kb-macos-arm64 and kb-macos-x64. It was absent before that because nobody here runs macOS and a published artifact would have been one nothing had ever executed; each one is now built and executed on a native runner of its own architecture, which is what answered the objection.
A hosted instance
None, and none to point at: the index lives beside the files and nothing talks to a server. Its line is under kept possible, not built on What Is Next.

Last read at commit 645bd0a on 8 September 2026, which added the source records and moved the verb count and the list of check codes on the Reference. This line moves whenever a number on any docs page changes. The retrieval figures the docs quote are older and are unchanged by it: the abstention re-run of 2 September 2026, made at commit c8c3890 with the scaled floor applied, and the floor itself, which landed as ea43d1d on the same day.

Next: Concepts · Back to the library