Customers do not start over.
Carry sourced facts across calls, chats, and days.
remember → recall
Customer memory with an action check
ContextDB carries sourced customer context across conversations, then checks remembered evidence before your host books, refunds, or changes a record.
remembered evidence × policy → act | ask | abstain
Three reasons to use ContextDB
Carry sourced facts across calls, chats, and days.
remember → recall
Correct or retract memory with explicit operations and lineage.
ADD · UPDATE · DELETE · NOOP
Connect the intended action to policy, evidence, reason, and result.
decision → evidence → receipt
Formation → Memory Evolution → Memory CI → Managed Sources → AI agent memory field guide →
Voice teams check appointment memory before booking. Support teams check account context before issuing a credit or changing a plan.
One reviewable decision
A tentative Friday conflicts with confirmed Thursday. Policy returns
ask, and the host reports that it skipped the booking.
ContextDB advises. The customer host authenticates, authorizes, and enforces. A receipt records what the host reported, not independent proof of downstream state.
Choose the operating path
Compare local and Cloud responsibilities → Inspect API contracts →
No. ContextDB returns an advisory decision. Your host enforces it.
Current business state stays in your system of record.
Install pycontextdb==0.4.4 locally and run one action check.
Remember one detail, evaluate it, and inspect the decision.