WHITE PAPER · MAY 2026
The CD Player Problem
A smarter remote does not change the medium. This paper asks whether connecting AI to existing systems is enough – or whether enterprise intelligence needs a different foundation for memory.
01 · THE METAPHOR
A robotic arm can change the CD. It cannot change what a CD makes possible.
The paper compares protocol adapters to a robotic arm operating a CD player: technically useful, but still constrained by the underlying format. Its argument is not that connectivity has no value. It is that improved access alone does not establish persistent context, relationships, or awareness of change.
What changes when memory becomes the foundation?
A condensed summary of the paper’s architectural argument, not a universal description of every MCP implementation.
Dimension | Adapter-centered approach in the paper | Unified-memory approach in the paper |
|---|---|---|
Data access | Fetch records on demand through APIs. | Maintain persistent, indexed organizational context. |
Relationships | Assemble context from separately retrieved records. | Represent connections between business objects. |
State over time | Work primarily with the state returned by each call. | Preserve history and meaningful changes. |
Actions | Operate on records through individual tool calls. | Coordinate actions across related context. |
Provenance | Evidence depends on what is retrieved and retained. | Connect answers and actions to source records. |
Three questions to take into your next evaluation
Ask for a demonstration, not just a claim. Use these questions to inspect where context lives, how it connects, and what survives across interactions.
01 · Where does context live?
Look beyond a single prompt. Ask what is persistent, how it is maintained, and how source evidence is retained.
02 · Can it connect domains?
Test an example that spans support, engineering, and account history. Inspect the relationships behind the answer.
03 · Does it know what changed?
Ask for a comparison across time, not only the current state. Check how the system explains meaningful changes.
Stop changing CDs. Start examining the architecture.
Our customers
Resources
Initiatives
