Docs
Docs your agents read before they start.
Your team writes the pages. Each run reads them before it starts, with nothing to set up, and notes which revision it read. When an agent learns something, it comes back to you as an edit to approve.
Writing
Write it together.
A page tree for the whole org and for each project.
- Spaces and pagesThere’s a space for the org and one for each project. Drag pages around the tree to reorder them, keep a space private, restore an old version, or leave a comment inline.
- An editor with the parts engineers useSlash commands, callouts, Mermaid diagrams, tables, code blocks, and links to pages and tickets. Turn on live co-editing for any space that wants it.
- Backlinks and templatesEvery page shows the pages and tickets that link to it. Start from a decision record, a runbook, an RFC or a post-mortem, or save your own template.
Reading
Read at the start of each run.
You don’t have to wire anything up.
- Essential and relevant pagesA run starts with the pages marked essential and up to six more that fit its ticket. The revision of each one is saved with the run.
- A snapshot it can searchWhen a run starts, the agent gets a read-only snapshot of up to 500 pages. It can search those pages and memory together.
Writing back
Agents suggest. People decide.
Anything a run learns comes back as an edit for a person to approve.
- Change-sets on the ticketA run’s edits are gathered into one change-set on its ticket, with a diff and a fit check that tells you whether it applies cleanly, merges with later edits or conflicts.
- Approve from the chatApprove or reject in Review, or from the card above the agent’s chat, without leaving the conversation.
Keeping it right
Up to date, and easy to take with you.
Pages carry a verified date, and nothing is locked in.
- Verified pagesVerify a page for a week, a month, three months or six. When it lapses it shows as stale and its owner is reminded.
- Export, mirror, importExport a page as Markdown, HTML or PDF, or a whole space as a zip. Mirror a space one way to a GitHub repo as a pull request, or import from Confluence.
How it works
How docs reach a run
- WriteYour team writes and verifies the pages.
- PinEach run gets the essential and relevant pages and a snapshot.
- RecordThe revision it read is saved with the run.
- ProposeWhat it learns comes back as edits to approve.
Questions
Asked about docs.
Is search semantic?
No. It’s keyword search across pages and memory together, and private spaces are filtered out inside the search itself.
Can agents change our docs?
Only as proposals a person approves, unless a space is set to let agent edits apply directly. The default is to propose.
The waitlist