Obsidian vault as storage layer, daemon outside the plugin sandbox

When a user wants an ambient context-aware tool and already has an Obsidian vault, resist building it as an Obsidian plugin. Plugins cannot register a global hotkey while Obsidian is closed, cannot read the frontmost macOS app, and stop existing when the app quits — all of which an ambient trigger surface requires. The right split is vault-as-storage (plain markdown + frontmatter + wikilinks, so context stays portable, greppable, and mobile-syncable) with the daemon living outside it. Also worth noting for scoping conversations: in this class of tool the capture box is trivial and the trigger engine (tasks carrying evaluable conditions like frontmost-app or active git repo, polled on a tick) is the real product — scope v1 around the trigger engine and note that dev-context signals need zero OAuth, so the core loop can be proven before any credential wiring.