Role
Stores durable context in plain files instead of chat history or app state.
Component / Source
Markdown vault
The durable source of truth: Markdown files, folders, WikiLinks, frontmatter, notes, project context, decisions, and references that stay readable outside any app.
Contains
- Markdown notes and project pages
- WikiLinks and folders
- Daily capture and reference material
- Source-backed context with provenance
Interfaces
- Obsidian reads and edits it
- Hermes can search/read bounded subsets
- Git/iCloud/Mac vault remains the canonical commit source
Maintenance rule
Prefer durable Markdown records with source links over raw chat transcripts or hidden app state.
Reliability signal
A useful note can be reopened later, linked to related context, and traced back to where it came from.
What goes in
Raw capture becomes durable only when the note keeps enough source, context, and links that a future reader can reconstruct why it exists.
What comes out
The output is not more notes; it is reusable context that can feed project pages, decisions, tasks, and agent prompts without private chat archaeology.
Quality check
Can the note be reopened without the original chat, can a source be traced, and can another page link to it without copying private context?
Concrete example
A project decision should keep the decision text, related project link, source or meeting note, status, and follow-up path. That makes it reusable by a human in Obsidian and by an agent summarizing project state later.
What stays private
Examples should describe the shape of durable notes without exposing private people notes, raw transcripts, or sensitive vault contents.
Failure mode: If this layer is vague, every agent and app invents context again.