Knowledge base
Each project brings its own knowledge base; the studio and the agents read and write it through a plugin.
The knowledge base holds what the team knows about the product: requirements, decisions, research, plans, and reports. It's the bridge between the product loop and the factory, so it lives in a tool the team already uses, chosen per project.
Plugins
| Tool | Status |
|---|---|
| Markdown in a GitHub repository | Planned first: versioned, reviewable, and readable by agents through the GitHub App |
| Confluence | Planned |
| Outline | Planned |
| Notion | Planned |
Every plugin implements the same contract: list and search pages, read a page with its version, create and update pages from templates. The studio and the agents only see that contract, so a project can switch tools without changing the factory.
What goes where
| Page | Written by | Read by |
|---|---|---|
| Requirement | The team, in the studio | Triage, Plan, QA |
| Decision record | The team | Everyone |
| Plan | The planning agent | Implement, Review |
| Status report | An agent, reviewed by a person | Stakeholders |