obsidian-memory-closeoutlisted

# Obsidian Memory Closeout ## Principle Memory is both input and output. Query relevant existing notes before acting, then write durable, curated updates into an Obsidian-compatible Markdown vault after useful work happens. Do not wait for the user to explicitly ask for memory updates when durable information emerges and a vault path or memory contract is available. Proactively decide whether to update an existing note, write a curated note, create a decision, create a session summary, or leave a proposal. Do not store raw transcripts, secrets, credentials, sensitive claims, unnecessary personal details, or noisy command logs. Prefer explicit notes, traceable sources, and small updates over archival dumps. ## Locate The Vault Use the first available source: 1. A vault path explicitly provided by the user. 2. `OBSIDIAN_VAULT_PATH`, `MEMORY_VAULT_PATH`, or a similar environment variable. 3. The current working directory, if it looks like an Obsidian vault or memory repo. 4. Ask the user for the vault path when none can be inferred safely. Before querying or writing, inspect local conventions: `AGENTS.md`, `.gitignore`, `.graphifyignore`, templates, and existing note structure. ## Before Work / During Work / Closeout ### Before Work / Query Read Before Work is mandatory before meaningful work on an existing project, decision, preference, or open loop when relevant memory is available. When a vault path or memory contract is available before meaningful work, read rele