project-wiki

You can create a persistent project wiki by initializing a docs/src/wiki directory to capture sources, concepts, decisions, and analyses. This establishes a team-visible knowledge base that grows with ingested documents and session decisions.

Automatically synthesizing glossaries and overviews works by ingesting documents into the wiki system, which then updates pages with domain terms and architectural decisions. This ensures long-term accessibility beyond ephemeral memory.

Preserving architectural decisions and domain terms is best achieved by maintaining a persistent wiki that integrates glossary and overview updates. It serves as a central reference during project work, enabling quick retrieval for collaborators.

Yes, you can ingest scattered codebase conversations and documents into a wiki to organize project knowledge. The system applies during active project work to synthesize pages for sources, concepts, decisions, and analyses automatically.

Yes, the wiki supports workflow-driven page creation and editing during active development. It ensures a consistent docs/src/wiki structure and provides fast retrieval of synthesized project knowledge for all collaborators.

Maintaining a project wiki prevents knowledge loss because it preserves a team-visible record in docs/src/wiki that grows with ingested documents. Ephemeral memory from chat sessions lacks long-term accessibility for future collaborators.