jason
d90abde29e
Rename echo-memory/ECHO -> quicksilver/Quicksilver throughout and make the plugin self-configuring per operator: - First-run flow: prompt for endpoint FQDN, API key, and operator name/role; verify; persist to a local config file (~/.quicksilver/quicksilver-config.json). - Two-layer setup detection: local config (is this install configured?) + in-vault marker (is the vault scaffolded?). Key never stored in the vault. - Replace hardcoded endpoint/key in all curl examples with $BASE/$AUTH loaded from the config file. - Genericize all "Jason"/"Bryan goldbrain"/MPM/wISP references to "the operator"; keep Jason as architect credit (README + plugin.json author). - Personalize memory to the configured operator (name/role seeded into operator-preferences and the vault marker). - Add echo-vault.md -> quicksilver-vault.md rename migration. - Rebuild packaged quicksilver.plugin; add docs/quicksilver-plan.md. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Quicksilver Memory Vault
This Obsidian vault is the persistent memory substrate ("second brain") for its operator. It is read and written across Claude / CoWork sessions through the Obsidian Local REST API.
This vault holds data, not logic. All operating procedure — how the vault is bootstrapped, how notes are routed, the taxonomy, frontmatter conventions, and safety rules — lives in the quicksilver plugin, which is the single source of truth. There are intentionally no CLAUDE.md / BOOTSTRAP.md / STRUCTURE.md control docs in this vault; updating or porting Quicksilver means updating or installing the plugin, not editing files here.
- Layout: see the plugin's
references/vault-layout.md. - Operating contract & safety: see the plugin's
references/operating-contract.md. - Bootstrap / repair: see the plugin's
references/bootstrap.md. - Version marker:
_agent/quicksilver-vault.mdrecords the schema version and bootstrap date.
Folders: inbox/, journal/, projects/, areas/, resources/, decisions/, reviews/, archive/, and the agent subtree _agent/.