01Why MOPS
Persistent memory is becoming infrastructure.
AI systems can retain preferences, decisions, project context and accumulated history beyond a single interaction. As that memory begins to shape future actions, other parts of the system depend on it being stable, understandable and trustworthy.
Memory contained within one application can be governed by that application. Memory designed to last for years, support multiple Agents and remain useful through changes in models, devices and storage needs a foundation that remains consistent across those changes.
MOPS provides a shared protocol foundation for that persistent layer.
02A changing ecosystem
The systems around memory will keep changing.
Models will be upgraded. Applications will be rebuilt. Agents will become more specialised. Devices, storage systems and vendors will change. Persistent memory may remain in use across many generations of these systems.
That ongoing change is the normal condition of a developing AI ecosystem. A durable memory layer should support it.
Persistent memory therefore needs a stable identity, structure and history that conformant implementations can understand and continue.
03Common ground
Shared semantics connect independent systems.
Applications, Agent frameworks, device runtimes and vendor platforms can each create coherent memory systems. When persistent memory moves between them—or is shared across them—shared semantics give participating systems a consistent basis for interpretation.
That shared layer establishes what the memory represents, how it is structured, which changes are valid, who has authority and which history is authoritative.
Independent implementations can then preserve the same meaning and be tested against the same expectations. Each new participant begins from established common ground rather than creating another interpretation of memory.
As the ecosystem expands, that common ground supports both continuity across time and coordination between systems.
04Continuity
Memory can remain continuous as implementations change.
Continuity means persistent memory can evolve while retaining a reliable account of its identity, structure, accepted changes and governing rules.
When a model is replaced, an application is rebuilt, a device reaches the end of its life or storage moves to a different architecture, shared semantics allow compatible implementations to carry forward both the current State and the lineage that gives it meaning.
MOPS establishes those semantics at the protocol layer. Memory can retain its defined meaning and history across conformant implementations, even as the systems processing and storing it change.
This gives compatible implementations a common basis for deliberate, verifiable migration and synchronisation. Meaning, lineage and governance remain part of what is preserved.
05Shared memory
Shared memory begins with shared meaning.
Continuity across time has a parallel requirement: coordination between multiple Agents.
Common rules allow them to agree on what the memory represents, which changes are valid, who may make them and which State is authoritative.
Each Agent can retain its own role, authority and visibility. The protocol provides shared semantics for expressing and enforcing those boundaries, allowing specialised Agents to coordinate around one reliable memory history.
A database provides durable storage. MOPS provides the common memory behaviour that Agents can share.
06Why a protocol
A neutral protocol gives independent systems a common foundation.
An organisation can build a strong internal memory system with its own structures, operations, governance and history. A protocol places the essential points of agreement in a neutral layer that independent implementations can adopt and test on equal terms.
A shared layer provides:
- common definitions for memory identity, structure, history and authority;
- common rules for valid changes and consistent outcomes;
- common tests for whether independent implementations preserve the same behaviour.
MOPS standardises this foundation while models, Agents, applications, runtimes, transport and physical storage remain open to implementation choice.
Implementations can use different code, databases and vendors while preserving the same shared protocol behaviour.
The goal is to make persistent memory the stable ground for everything else to develop around it.