memory-system

To persist Obsidian vault memory across sessions, this Skill loads identity, core memory, and recent daily notes for context, then applies backup-safe updates with deduplication and supersession handling to MEMORY.md. It uses deterministic file paths and structured frontmatter to ensure clean knowledge recall.

Memory decay in this vault-native system applies a hybrid approach during MEMORY.md updates that supersedes outdated facts without deleting them. This preserves historical knowledge graph integrity while ensuring current decision-making relies on the most relevant, recently confirmed information.

Yes, you can automate daily journal writing through scheduled extraction workflows that create or append structured entries to today's Daily Journal note. The system uses task data already present in the vault, applying consistent YAML frontmatter and wikilinks to maintain knowledge topology.

The best way to maintain vault knowledge topology is writing extracted entities into correct Projects, Shared Knowledge, and People locations with consistent YAML frontmatter and wikilinks. This Skill ensures deterministic file path targeting within the vault for all written notes.

Council integration acts as a gatekeeper by providing read-only context to Council and accepting council decision or verification records to write them safely into the vault. This process ties logs to specific deliberation identifiers for persistent, structured tracking.

You need backup-safe updates because read-first operations ensure original vault memory is preserved before applying deduplication, supersession, or decay logic. This prevents accidental data loss during automated workflows or interactive session updates, keeping your knowledge graph reliable.