This folder is the physical knowledge root. The Wiki renders this real folder tree directly: categories are directories, pages are Markdown or sandboxed HTML files, and there is no virtual grouping layer.
Use this page as the first stop when you need the right document quickly.
| Folder | What lives there |
|---|---|
| architecture/ | Architecture model, ADR archive, proposed ADRs, backend structure, bus docs, runner-lane constraints, and HTML maps. |
| domains/ | Current system-of-record domain maps for runner, pipeline, tasks, frontend, CLI, tokens, and token pricing. |
| contracts/ | Durable filesystem, task, protocol, run outcome, code-pattern, and wiki organization contracts. |
| product/ | Product and UX direction: design principles, orchestrator chat, companion app, and skills architecture. |
| frontend/ | Frontend design system, style guide, testing contract, performance playbook, and audits. |
| cli/ | Supported CLI contract, per-CLI skills, audits, and investigations. |
| operations/ | Setup, onboarding, security docs, runtime observability, git doctrine, and test workspaces. |
| reports/ | Report contracts, HTML visual reports, and screenshot-backed visual documentation. |
| meta/ | Document metadata, drift grading samples, direction, and HTML metadata reports. |
| concepts/ | Future/current architecture concepts that have not become a domain or ADR yet. |
| in-app-help/ | Short Markdown help pages served by the app next to non-obvious UI surfaces. |
| wiki/ | Living knowledge: common problems, explanatory concept pages, learnings, and migration notes. |
| research/ | Dated deep dives and decision grounding material. |
| schemas/ | JSON schemas for wire and disk shapes. |
| mockups/ | Locked design references and click-dummies. |
| assets/ | Image assets referenced by documentation pages. |
- Keep source-of-truth contracts in
domains/,contracts/, orarchitecture/. - Keep dated evidence in
reports/,research/,frontend/audits/, orcli/audits/. - Keep explanatory and evolving notes in
wiki/. - Use Markdown by default.
- Use HTML only for visual or spatial pages that need layout, such as maps or reports. HTML pages must be self-contained and readable in the Wiki iframe.
- When adding a new document, put it in its real category and add it to the nearest category index.