This project utilizes a codebase wiki at .codebase-wiki/ to maintain long-term architectural memory and conceptual alignment.
To ensure the knowledge base remains an accurate source of truth, the agent must follow these protocols:
Whenever a significant architectural decision, new module, or major feature is implemented, the agent must update the wiki.
- What to update: Update relevant entity pages, create new concept pages, or add an ADR (Architecture Decision Record).
- How to update: Use
wiki_ingestfor automated updates andwiki_entity,wiki_concept, orwiki_decisionfor manual, precise additions.
Before implementing complex features or making architectural changes:
- Search: Use
wiki_queryto check for existing patterns, decisions, or constraints. - Cross-Reference: Check the
[[INDEX]]and related entities to understand dependencies. - Validate: Ensure new changes don't contradict accepted ADRs.
Every few sessions or after a large feature merge, the agent should:
- Run
wiki_ingest source=smartto pick up recent git commits and file changes. - Run
wiki_lintto find broken links, orphan pages, or contradictions. - Resolve contradictions by merging duplicates or adding cross-references.
- Enrich "stub" pages (those with "(to be discovered)") using
wiki_ingest source=llm.
wiki_query: Primary method for retrieving project knowledge.wiki_ingest: Synchronizes the wiki with the current codebase.wiki_lint: Quality assurance for the knowledge base.wiki_entity/wiki_concept/wiki_decision: Precise manual updates.
The wiki is the brain of the project. Keep it healthy, keep it current. 🐉