Domains / vault-memory
Vault Memory domain
A personal or team memory vault: raw captures become drafts, and only distilled knowledge becomes memory.
Use it when: You want an agent to turn notes, links, and files into a typed knowledge graph.
cumaru install agent <agent> --domain vault-memory Pillars
| Pillar | Lifetime | Holds |
|---|---|---|
memories/ | Durable | Canonical memory nodes with typed graph relationships. |
attachments/ | Durable | Source files that must outlive inbox cleanup. |
drafts/ | Durable | Rough thinking that may or may not become memory. |
inbox/ | Transient | Raw captures; processed captures are removed by default. |
Roles
- Keeper: the vault role defined in roles/keeper.md.
Lifecycle
- inbox/ -> drafts/ -> memories/, with attachments/ when sources must be kept.
- Capture, distill, link, then clean up. The inbox is not archival storage.
Skills
Domain-specific skills, in addition to the universal ones: cumaru-capture,cumaru-draft,cumaru-distill,cumaru-link.
Bootstrap
No domain bootstrap document and no migration document.
Domain rules
- Graph edges live in frontmatter: relates, supports, contradicts, supersedes, superseded-by, part-of, similar-to, derived-from.
Example: Keep one useful idea from an article
- cumaru-capture stores the URL in inbox/.
- cumaru-distill writes one memory node with derived-from pointing at the source.
- cumaru-link adds supports and contradicts edges; the capture is removed.
Source: domain.md, config.yaml, roles, skills at revision 37ad79f. The example is a summary
of the shipped recipes, not CLI output.