Memory Layer Portability Audit (Handoff)

Memory Layer Portability Audit (Handoff)

1. 01

   Inventory every agent memory store currently holding client context

   List each connector by name and the accounts it serves. Bourdon federates memory across Claude, Codex, and Cursor, so a single store may already span several client engagements.

2. 02

   Test a full export of one client's memory set before renewal talks begin

   Pull the raw export, not a screenshot of the UI. If the vendor returns a proprietary blob with no readable schema, treat that as a lock-in flag.

3. 03

   Map each stored entity to the client deliverable it supports

   Tag entries as brand rules, architectural decisions, debugging discoveries, or campaign history. Knownbase organizes notes by project and tag, which makes this mapping fast when the archive is structured.

4. 04

   Score retrieval quality on a fixed 20-question recall test

   Ask the same questions of each store and record hit rate and latency. Graph-based systems such as Cogni retrieve connected facts through spreading activation, so multi-hop questions separate them from plain vector search.

5. 05

   Confirm the memory layer survives a model swap

   Re-run the recall test against a different LLM. A connector that only works with one provider is a single point of failure for every retainer built on it.

6. 06

   Document the migration path in the client contract

   State who owns the memory data, how it leaves the platform, and in what format. Institutional knowledge that cannot be exported is a liability at handoff, not an asset.

7. 07

   Set a quarterly re-audit date and assign an owner

   Memory stores drift as agents write new notes. Without a named owner, stale entries quietly poison recall for the next team.