Wiki

The wiki is your project’s encyclopedia. The tree shows the project’s structure; the wiki holds what the structure alone can’t tell you — how each part works, which rules must be kept, and what the words used in the project mean. Your AI agent writes the wiki, and you read it on the app’s Wiki screen.

Table of contents

Wiki pages are joined into one table of contents. The overview sits at the top, with chapters (concepts, architecture, operations, glossary and so on) and entries below it in order. The Wiki screen numbers them in that order, so reading from the start walks you through the whole project.

When starting a new wiki, the agent follows a recommended table of contents for the kind of project (web service, app service or library).

Shape of a page

Every page follows the same skeleton.

• Lead: one or two sentences on what the page is about
• Spec: how it works now
• Rules: what must be kept
• Notes (footnotes): background, history and side notes, moved to the end to keep the body light

Each page has a kind (overview, concept, component, rule, glossary), and its title is a short name like “Billing” or “Deployment”. When a page strays from this shape, the agent gets a warning as it writes and fixes it.

History

Every edit keeps the previous version as a revision, so you can always go back. The wiki records “how things are now”, not a work log — when something changes, the sentence is rewritten rather than added to.