Direct answer: What should AI agent memory store in wealth management?
AI agent memory in wealth management should store durable preferences, validated facts, source references, workflow state, and prior approved decisions separately. A chat transcript is not enough because financial memory must be current, attributable, permissioned, and safe to reuse.
How Celestice helps
Celestice treats memory as governed financial context, not a loose chat history. In practice, task-specific context packs can combine validated facts, preferences, source references, approvals, and workflow state while keeping sensitive account data scoped to the work that needs it.
<!-- celestice-query-answer:end -->Two failure modes, one hard problem
An AI assistant for your finances faces a deceptively difficult challenge with memory. Fail one way and it is maddening: it forgets what you told it last week and makes you re-enter your goals, accounts, and preferences every session. Fail the other way and it is dangerous: it treats a months-old chat comment as a current fact and acts on stale or casual information as if it were verified financial truth. The right design threads this needle — it should not make you repeat what is already known, but it must never treat a long chat transcript as reliable financial memory.
The core insight: not all memory is equal
The mistake most AI systems make is lumping everything into one undifferentiated context blob — the whole conversation, pasted in and trusted equally. Serious memory design separates distinct kinds of information that deserve very different trust and handling:
- Current state — what is true right now: holdings, balances, the screen you are on, the entity you have selected.
- Validated outcomes — results of work that actually completed and was verified, not just discussed.
- Durable facts and preferences — stable truths: your risk tolerance, your goals, your household structure, restrictions you have set.
- References — the documents, policies, and evidence that back a claim.
- Workflow resume state — where a multi-step process left off so it can pick up cleanly.
Keeping these separate is what lets the assistant be helpful about what it remembers while being disciplined about what it trusts.
Episodic vs semantic memory
Two of these deserve a closer look because they map to how durable knowledge actually forms. Episodic memory is the record of specific events — "on this date, this conversion was reviewed and approved." Semantic memory is the stable, distilled knowledge — "this client prefers tax efficiency over maximizing pre-tax growth." Episodic memories are the raw events; semantic facts are what you learn from many of them. A casual remark in one chat is an episode, not yet a durable fact — and treating it as a settled preference before it has been confirmed is exactly the overreach to avoid.
Building a context pack: prioritize the task at hand
When the assistant assembles context for a task, more is not better — relevance is better. A well-built context pack prioritizes the current task in roughly this order: the current goal, the current screen and selected entities, the relevant activity and open decisions, the evidence in play, then relevant episodic memory, and finally the stable semantic facts and preferences. This ordering keeps the assistant focused on what you are doing right now, drawing on history only where it is actually pertinent — rather than dumping an entire relationship history into every request and hoping the model sorts it out.
