Documentation · Documents
Project documents
Every project carries a living documentation wiki with two clearly separated sections: the plan you approved, and documentation generated from the code as it grows. The platform never blurs the two.
Charter vs. generated
| Section | Contains | Who changes it |
|---|---|---|
| Charter — approved plan | User Brief, Understanding Document, Constitution, Solution Architecture Document, and any pages you write yourself. | Only you (edit/refine/approve). Merges and re-indexing never touch charter documents. |
| Generated from code | The As-Built Architecture page and per-component deep-dives — living documentation of what actually exists in the repository. | The platform, after every merge — updated accretively: new work is integrated, and components from earlier merges never shrink or disappear. |
Working with a document
- Refine — type what you want changed in plain language. The AI rewrites only the sections your feedback touches; everything else is preserved byte-for-byte. Cheap enough to iterate freely.
- Edit — direct Markdown editing when you want exact control.
- Regenerate — rebuilds the document from its template and fresh context; use when the plan changed fundamentally.
- Approve — locks the exact content as the plan. Any later edit, refine, or regenerate resets it to draft, and ticket dispatching pauses until you re-approve — approval always refers to content you've actually seen.
- History — every version of every document is kept; restore any of them.
Long operations survive navigation: while a refine or regeneration runs, the document shows a server-tracked progress banner and disabled actions — leave the page, come back, it's still visibly working, and updates in place when done.