This section documents practical patterns for structuring KEGs so project memory stays useful to both people and AI agents.
Before adding lots of notes, decide:
- which domains belong in shared organization kegs
- which domains need private or restricted kegs
- how tags are used for slicing and filtering
- whether multiple domains should share one keg or be split
Early decisions here reduce onboarding friction and make long-term recall more reliable.
- Create your initial structure with minimum required node files: Minimum Keg Node
- Split low-overlap domains into separate kegs when needed: Domain Separation And Migration
- Use concrete starter layouts by domain: Example Keg Structures
- Apply consistent note writing conventions: Markdown Style Guide
- Prefer one keg per high-level domain when cross-links are rare.
- Keep zero node (
0) as a stable landing node in every keg.