Xerum for investment and financial services teams
What did we know, and when did we know it
For most teams that is a curiosity. For yours it is a question somebody with subpoena power may ask, and the honest answer has to come out of a system that could not have been edited afterwards.
Sound familiar?
The reasoning is not in the memo
The memo records the conclusion. The debate that produced it — what the dissent was, what assumption it turned on — is in a thread, and the thread is what somebody will want in two years.
Mutable stores cannot answer the question
A knowledge base that overwrites in place can tell you what it says today. It cannot tell you what it said on the day the decision was made, which is the only version that matters afterwards.
Access is not uniform, and cannot be
Deal teams, wall-crossed individuals, everyone else. A search tool that filters after ranking leaks the existence of what it hid, which in this setting is itself the disclosure.
What changes
Append-only by construction
There is no update path that overwrites what a resource used to say. A change appends and produces a new revision, so the history has the shape a reviewer expects.
Read at the revision that matters
Ask the context what it held on a given date and get the answer as of then, not as of now with the intervening edits folded in silently.
Attribution, never a service account
Every change names the person responsible. Agents act as the person they serve with user-bound tokens, so automation does not erase who did what.
Pre-filtered, before ranking
Permission filtering happens inside the query. Somebody outside a deal team gets results that do not reveal the deal exists — not a shorter list that implies it does.
What this industry buys
Versioning + audit
The compliance question and the data structure are the same thing here, which is the cheapest kind of alignment to have.
- Nothing is edited in place — ever, by anyone, including us
- Audit is reading the change log; there is no second system to reconcile
- Every change carries author, time and the message saying why
- Your own database and storage prefix, replicated per team
A record that answers the regulator, not just the analyst
Built today, not on a roadmap. Every property above is already how the store works.