What problem does it solve?
Keeps the memory vault consistent, discoverable, and reliable by prescribing folder locations, naming patterns, and usage rules so agents and humans avoid duplication, lost context, and messy RAG inputs.
Core Features & Use Cases
- Defines a canonical folder layout for daily logs, meetings, projects, clients, research, content, team context, and draft lifecycles to standardize where information is stored.
- Enforces naming conventions (date-first filenames and slugified titles), append-only daily logs, and one-entity-per-file rules to make long-term memory concise and loadable into every session.
- Manages draft lifecycles with active, sent, and expired buckets and requires checking for existing files before creating new ones to prevent duplicates.
- Use case: Save meeting notes to the meetings folder, keep a one-line pointer in the daily log, and keep MEMORY.md concise for fast context loading.
Quick Start
Save your sprint planning notes to meetings/2026-04-13-sprint-planning.md and add a one-line reference to today's daily log.