Client work without the context-switch tax.
Acme is net 30. Northwind bills on delivery. One of them hates bullet points. Your memory should know which is which — every time, without being told.
The problem, precisely
Client work is context switching as a full-time condition. Every client has terms, tools, names, sensitivities and history — and the cost of mixing them up ranges from embarrassing to contract-ending. An assistant with no memory makes you the lookup table. An assistant with one undifferentiated memory is worse: it will confidently apply Acme's billing terms to Northwind.
A scope per client
In Varven, each client is a scope — a namespace inside your vault. Ask about Acme and retrieval stays inside Acme's layers, plus the global band of preferences that are true everywhere. Ask across all clients on purpose — “who still owes a kickoff?” — and it widens, deliberately rather than by accident.
People and organisations, linked
Memories mention people, and Varven links them as it files. “What do I know about Dana?” pulls everything she appears in: the sign-off rule, the meeting where scope changed, which client she belongs to. The vault also keeps maps — people, organisations, decisions — regenerated as the record grows, so the entry points stay current without your maintaining an index by hand.
Facts age. The record says so.
A rate you quoted in January is not a fact forever. Varven tracks how long each kind of claim has gone unconfirmed — facts go stale in six months, events in one — and flags what nobody has re-checked, so “their contact is Sam” comes with a warning when it has been a year since anyone verified that. When terms change, the old layer is superseded, not erased: you can still answer “what were we charging them before the increase?”
Which plan this needs
At your desk, the free plan does all of this. Sync adds the cloud replica and a second device — useful the day you are at a client site and need last quarter's decision from your phone, with the office machine asleep.
Questions
Can one client's context leak into another's answers?
Searches filter to a scope, so a question about one client pulls only that client's layers plus global preferences. Cross-scope answers happen when you ask for them, not by default.
Can my clients see any of this?
No. The vault is Markdown on your machine. On paid plans the replica is private to your account — the security page spells out exactly what that involves, including what is not built yet. On the free plan there is no cloud copy at all.
What about work under NDA?
Keep it on the free Local plan and nothing leaves the machine. The confidential work page covers this in full.