context-vaultlisted

# Context Vault Context Vault is a durable, user-controlled project-memory layer. Its canonical data is standard Markdown beneath an Obsidian vault; the plugin never treats chat history as durable memory. Schema v2 vaults describe themselves: a generated `SCHEMA.md` at the record root is the full record contract (types, link discipline, relation registry, recording ladder), so any agent can read and write the vault without this plugin. When writing records by hand, follow it exactly; if this skill and a vault's SCHEMA.md disagree, the vault's SCHEMA.md is newer — follow it and say so. ## Model routing — write records with a cheap model **Read this before you write anything.** Composing a vault record is mechanical distillation: fixed fields, a handful of one-line values, a generated body. It is transcription, not reasoning, and it must never consume premium tokens. Decide *what* to record with the model driving the session; hand the *writing* to the cheapest model that can do it. In Claude Code, delegate with the Agent/Task tool, pinning the model: ```text Task(subagent_type: "general-purpose", model: "haiku", prompt: "Read <transcript path / these notes>. Then run exactly: python3 <resolved $CONTEXT_VAULT> propose-session \ --project <id> --kind wrapup --trigger wrapup --goal ... \ --session-id <id> \ --agent claude-code/haiku-4.5 Report the command you ran and its full output verbatim.")