Customer prefers architecture reviews to include a rollback plan and an explicit verification gate.
Memory with a control plane.
This demo shows the operating model: scoped memory, source-aware retrieval, explicit promotion, and refresh safety. It is a product walkthrough—not a live customer environment.
Scoped memory
The same agent can hold private, shared, and temporary context without mixing them.
Production changes require an isolated canary before the live deployment.
For this incident review, compare the current gateway route against the last known-good configuration.
Provenance-aware search
Every result carries enough context for a human to inspect where it came from.
Customer preference captured during onboarding; available only to the scoped user and agent.
Team policy promoted explicitly by an administrator.
Promotion policy
Shared memory is not a side effect. It is an explicit decision.
New memories stay scoped to the originating user and agent.
A human or approved policy promotes a memory into shared context.
Temporary investigation context expires with the run unless promoted.
Knowledge indexing does not write into production memory.
Safe refresh
A knowledge refresh should be boring, repeatable, and observable.
Record production memory count and current kg state.
Normalize paths, upsert Wiki and CodeGraph nodes, preserve provenance.
Refresh the knowledge-layer mirror without writing to public.mem0.
public.mem0 before: 326 · after: 326 · unchanged: true