Watch MultiVault actually work

TRIGGER — background watcher, 09:14:02

▸ fs event: ~/Vault/Contracts/Northwind_MSA_v4.pdf (modified, 214 KB)
▸ incremental index: 1 doc re-chunked, 38 terms updated, 41 ms
▸ index total: 1,847 docs · 12,203 chunks · calendar.ics (312 events)

RESULT — Claude Desktop, 09:31

You ask: "What did we actually commit to on Northwind's renewal, and when's the call?"

MCP call fires: get_context(query="Northwind renewal terms call", k=6)

Returned — BM25-ranked, not everything:
1. Northwind_MSA_v4.pdf §7.2 — auto-renew 12 mo unless notice ≥60 days before 2026-03-31 (score 18.4)
2. Northwind_MSA_v4.pdf §4.1 — uplift capped at CPI +3% (score 14.9)
3. email_export/2026-01-08_dana_northwind.md — "we'd want the cap in writing before signing" (score 11.2)
4. calendar.ics — 2026-02-04 10:00, "Northwind renewal — Dana Okafor, Priya" (score 9.8)
5–6. board_deck_Q4.md, pricing_notes.md (score <8, trimmed)

Claude answers from those six chunks. The other 12,197 never left the disk.

vault_status: encrypted AES-256-GCM · last index 09:14:02 · watcher live · 0 network calls this session
MultiWitness: event 4,412 logged — chain hash 9c1f…a30d, verified against 4,411

Honest limitation: MultiVault indexes a local folder and a calendar .ics file. It does not pull live from Gmail, Notion, HubSpot, or Drive. If Northwind's latest redline only exists in a Google Doc, it's invisible until it's exported into the vault folder — Drive desktop sync or a nightly export script closes that gap, and the watcher picks it up from there.