Agent memory fragmentation mirrors pre-2019 observability before OpenTelemetry merge

Fragmentation appears in at least seven distinct storage patterns documented in the LoreKit post: instruction files such as AGENTS.md, agent-managed files under /memories, GitHub Copilot repo facts with 28-day TTL, Letta labeled blocks, Mem0 extracted facts keyed by user_id, LangGraph namespaced stores, and temporal graphs from Graphiti. Each implements its own addressing and forgetting rules. The pattern matches OpenTracing versus OpenCensus competition that ended with their 2019 merger into OpenTelemetry, which standardized spans, metrics, logs, semantic conventions, and the OTLP protocol while leaving storage and analysis to vendors.

The absence of agreement creates direct operational risks beyond interoperability. Shared memory across agents can leak context containing API keys, user data, or proprietary code without explicit scope controls or audit trails. Privacy exposure scales with each new format because records lack standardized expiration, provenance, or access scopes. Misuse vectors include unauthorized cross-agent fact injection and persistent retention of sensitive observations that no single vendor can revoke.

Linux Foundation's Agentic AI Foundation already hosts MCP and AGENTS.md, providing a neutral venue comparable to the Cloud Native Computing Foundation's role in OpenTelemetry. Reference implementations and a minimal data model for scoped records with explicit lifetimes would allow vendors to compete on retrieval speed and reasoning layers rather than storage syntax. Without such convergence, each new memory tool adds another isolated silo.

Data from r/LocalLLaMA and r/cursor shows repeated reinvention of JSONL knowledge graphs and MCP servers, confirming demand while quantifying the coordination failure. A working group could publish an initial spec within six months if participants agree to freeze custom schemas.