wednesday-search — Hybrid search over operator’s Wednesday vault

Category: skills Where it works: Claude Code / Telegram (Hermes) / both

What it is

Hybrid lexical + semantic search over Wednesday’s indexed corpora. The preferred path is /search <query> through the runtime plugin; natural-language requests fall back to the same search script. Results come from one Postgres store and are fused by rank, rather than invented by the model.

How to trigger it

• “caută X în vault”
• “find Y in my notes”
• “ce-am scris despre Z”
• “/search ”
• “/ask”
• “/recall”

Direct command: /search <query> (preferred — handled by plugin, no LLM round-trip).

Auto-fires? no — explicit trigger required.

How to use it

Operator sends /search <query> or a natural phrase. The plugin/script returns the strongest matches with source, path and snippet. If there is no relevant result, Wednesday says so plainly. A full-file read is a separate explicit step.

Practical examples

1. You: /search deployment checklist → returns ranked snippets from the indexed vault.
2. You: “ce-am scris despre retenția backupurilor?” → returns grounded matches or a clear no-result message.

Notes / limits

• --source and --folder can hard-scope both lexical and semantic search.
• This lane searches indexed corpora; explicit Grimoire note operations use the Obsidian app or Obsidian MCP.
• Don’t fabricate results or silently pad a weak result set.