Durable project level memory
Map
./workflow/: docs for the development workflow
./findings/: non-code deliverables for an issue in ./findings/<issue-id>-<slug>.md
Rules
Update the wiki when you discover information that would likely help:
- future task execution
- debugging
- onboarding
- architectural consistency
- operational reliability
- repeated workflows
Good wiki updates include:
- architectural decisions
- debugging discoveries
- workflow improvements
- conventions
- caveats and gotchas
- operational runbooks
- reusable commands
- integration notes
Do NOT add:
- temporary notes
- obvious information
- duplicate content
- speculative ideas without validation
Favor concise, high-signal additions.
Prefer improving existing knowledge density over expanding page count.
Write for future agents and humans, not for historical completeness.
Cross-link related pages when relevant.
Before updating the wiki:
- distill the learning
- remove task-specific noise
- preserve only reusable insight
Create new pages only when:
- the topic is substantial
- the information does not fit existing structure
- the topic is likely to grow independently