Wikis

A wiki is your workspace's knowledge base: a structured set of pages, kept fresh from raw source material, that every agent in the workspace can read. One workspace, one wiki.

Why wikis are a primitive

Resources point an agent at data that already exists in the right shape. A wiki goes further: it owns the shape. You hand it raw inputs — uploaded files, web pages, notes — and Levain distills them into pages organised under a table of contents you control.

That separation buys you two things:

• Agents read clean pages. They don't need to track where a fact came from or when the underlying file last changed — the wiki abstracts that away.
• Pages stay coherent over time. When new material contradicts old material, the wiki reconciles them in place instead of stacking yet another file on the pile.

The shape of a wiki

A wiki has three layers:

• Sources — the raw material. PDFs, markdown files, text snippets you upload. Each source is immutable; replace one by deleting it and uploading a new copy.
• Schema — the table of contents. A plain-markdown list of page paths with a short description of what each should cover.
• Pages — the maintained output. Markdown files at the paths declared in the schema, kept in sync with the underlying sources.

You write the schema. Levain writes the pages. Other agents read both.

Always-on maintenance

Every wiki has a dedicated maintainer that wakes up whenever new sources arrive or you ask for a refresh. The maintainer reads the schema, reads the sources, and rewrites the pages so they reflect the current state of the material. Maintenance runs on Levain's account — keeping a fresh wiki costs you nothing.

Reads never block on maintenance: agents always see the last committed pages, even when a refresh is in flight.

Next

• The Knowledge Base guide walks through seeding sources, evolving the schema, and reading pages — end to end.
• The Wikis API reference covers every endpoint if you want to script it.