Knowledge Base
Seed sources, shape the schema, read maintained pages.
The wiki is your workspace's knowledge base. This guide walks through the lifecycle: getting raw material into the wiki, telling Levain how the pages should be organised, and reading those pages from your agents.
Open the Knowledge Base
In the dashboard, Knowledge Base is in the left sidebar. It opens on the pages tree — the maintained output. New workspaces start empty, with a friendly nudge pointing at the Sources tab.
Add sources
The Sources tab is where raw material goes in. Drop files anywhere on the page or use the Upload button. Markdown, plain text, PDFs, and images are all accepted, up to 25 MB per file.
Sources land in a Pending section first. When you're ready, click Process — the maintainer reads the new material and writes the corresponding pages. Processed sources move to the Processed section, and the new pages appear in the tree on the Pages view.
Sources are kept around so you can audit what the wiki was built from. Deleting a source removes the raw file; pages it produced stay until the next maintainer pass reconciles the change.
Shape the schema
The schema is the table of contents the wiki commits to — a list of page paths with a short description of what each should cover. Edit it from the dashboard the same way you edit any markdown document, and the maintainer reorganises pages on its next run: pages removed from the schema are dropped, new entries are written from sources already in the wiki.
Read pages from an agent
Every agent in the workspace can read the wiki at runtime. The pages tree in the dashboard is what your agents see too — pick a page in the tree to view its current content.
Pages always reflect the last committed maintainer run, even while a refresh is in flight, so agents never read half-written content.
Refresh on demand
The maintainer runs automatically whenever new sources land. To force a fresh pass — after a schema change, or just to re-distill what's already there — click Process on the Sources tab. The refresh shows up in your workspace history like any other run.
From the API
Everything above has an API equivalent if you'd rather script it: upload sources, edit the schema, list pages, and trigger a refresh. See the Wikis API reference for the full surface.
Next
- The Wikis primitive covers what the maintainer is and how it fits into the platform.
- The Recipes guide shows how to wire wiki reads into your agent's logic.