Watch MultiVault actually work

Scenario: Priya, ops lead at a 9-person SaaS co, opens Claude Desktop Monday 8:41am to draft the board update.

▸ Local snapshot (CLI, run by her Monday cron)

$ multivault snapshot --folder ~/Ops/BoardQ3 --cal ~/Calendars/priya.ics
Passphrase: ********
scrypt N=2^17 … key derived (1.4s)
Indexed 31 files (2.7 MB) — runway_model_v4.xlsx, churn_notes.md,
hiring_plan.md, investor_update_draft.md, 27 more
Calendar: 44 events, Oct 1 – Nov 15
Sealed → ~/.multivault/boardq3.vault (AES-256-GCM) — 0 network calls

▸ MCP call from Claude Desktop

tool: get_context scope="last 14 days + upcoming week"
→ 6 files, 11 events returned in 380ms, loopback only

Claude now has: churn_notes.md (3 logo losses, $4.1k MRR),
runway_model_v4 (14.2 mo at current burn), and calendar entries
"Series A prep — Kleiner" (Nov 4), "Comp review w/ Dana" (Nov 7).

Draft opens: "Q3 closed at $61.4k MRR, up 8.3%. Three churned
accounts concentrated in the sub-$500 tier…"

▸ vault_status → sealed_at 08:00:04, 31 files, chain height 212

▸ MultiWitness → 212 | get_context | sha256:9f3a…c1d7 | prev:41be…88a2

Honest limit: it's a snapshot, not a live sync — files edited at 10am aren't visible until the next snapshot runs. And it's one folder plus one calendar file per vault. If your context lives across Notion, Drive, and Slack simultaneously, this covers the folder, not those.