Operating memory is the retained state of work — facts, evidence, decisions, approvals, assumptions, unresolved risks, artifacts and workflow state — scoped to where it belongs.
Keep the state of the work
A business records a great deal: a request in email, a contract in documents, a payment in finance and a decision in a meeting. The next person needs the relationship between them. What was agreed? Which evidence mattered? Who approved it? What is still unresolved?
Operating memory carries that relationship forward. The useful unit is a workflow with its evidence, authority, output and current state. An artifact is simply the result someone can use: a brief, report, proposal, decision packet or action plan.
Consider a contract dispute settled in March. The next claim should begin with the accepted interpretation, its source, the person who authorised it and any remaining conditions. That gives the reviewer a prior position to check and update.
What a useful memory contains
| Retained context | Why the next run needs it |
|---|---|
| Facts and source evidence | Trace a statement to the material supporting it. |
| Decisions and approvals | Understand the reasoning and the person with authority. |
| Assumptions and open risks | See what still needs checking or resolution. |
| Outputs and workflow state | Continue from the last accepted result and next action. |
| Corrections and superseded positions | Use the current position while keeping the change understandable. |
Provenance, time, confidence, review status and scope travel with the information. A provisional belief remains provisional until evidence or an authorised review supports a stronger status. A newer decision can supersede an earlier one while preserving its history.
Watch the context become useful
The sequence below follows one decision: sources connect, a recommendation takes shape, a person reviews it, and the accepted outcome becomes context for the next run. Each stage shows a different responsibility.
- 01 / Connect
The evidence finds its context.
Sources arrive with their provenance. The connected picture shows what supports the decision and what still needs checking.
- 02 / Prepare
One recommendation takes shape.
Morpheus assembles the evidence and prior decisions into a reviewable proposal. The source relationships remain attached.
- 03 / Review
A person owns the decision.
The amber gate marks the review. The accountable person accepts, corrects or holds the proposed action.
- 04 / Retain
The outcome becomes memory.
The accepted result, reasoning and approval return to the context of the work with their status and scope.
- 05 / Reuse
The next run begins further ahead.
The connected memory grows. Later work can recall that reviewed position, inspect its evidence and update it as conditions change.
Give memory a clear home
Context belongs to a defined channel, workspace, organisation or customer instance. A team needs the information it is entitled to use, with the permissions and purpose attached. Scope is therefore part of the meaning of operating memory.
One organisation can have one or many instances. Each instance contains one or many workspaces; each workspace can run one or many playbooks. The Mesh connects instances through approved exchanges while each keeps its private memory within its own boundary.
For an international business, that structure can separate regional operations and still connect authorised results. Explore instances, workspaces, playbooks and the Mesh.
- 01 / Instance
Give operations a clear boundary.
An organisation can have one instance or many. Each provides an operating boundary for its application, database and resident memory.
- 02 / Workspace
Organise the work inside it.
One instance can contain many workspaces. Teams, customers and functions can each work within an appropriate scope.
- 03 / Workflow
Run the repeatable work.
A workspace can run many playbooks. Each defines a workflow’s inputs, output, tools, approval point and retained state.
- 04 / Capability
Package a governed result.
A proven workflow can be packaged as a capability with its policy, required information and expected result attached.
- 05 / Mesh
Connect instances through the Mesh.
Instances exchange approved results while retaining their own private memory. Instance connectivity runs on customer zero; cross-instance capability calls are in development.
Remember in service of an objective
Memory becomes useful when the system knows what the work is trying to achieve. Objectives can sit at organisation, workspace, workflow, role and task level. Each carries its owner, scope and relevant constraints; weight, confidence and source help explain how it should influence a decision.
An objective such as protecting a warranty changes which dates and service records matter. A missed service intervention becomes something the team can investigate, correct and check on the next run. Read how objectives guide improvement.
The objects that carry the work
Three jobs organise the product: remember the context, govern the decision and execute the agreed workflow. An evidence room gathers sources and gaps. A decision room holds a question, options and reasoning. Approval trails record who accepted an action. Workflow packages bring the inputs, output, approval model and retained state together.
Operating-memory foundations, objective hierarchy and autonomy controls are live. Evidence rooms, approval trails and workflow packages are available in selected workflows; decision rooms are in private preview. These statuses describe the scope in which each object can currently be used.
Bring the context to the team
Workspaces bring chats, playbooks, reports, files and memory together. Channels bring governed conversations into the places people use. Apps provide a focused output such as a portal, calculator or review queue. Connectors let the workflow reach authorised information in existing tools.
Cortex helps examine what has been learned; Eye makes cross-workspace activity and decisions visible for review. People can inspect, correct and accept the context that will influence later work. Explore that review loop.
How it works with existing systems
Systems of record continue to own their records. Retrieval finds relevant material; orchestration runs steps; operating memory connects evidence, decisions, authority and unresolved state across those runs. These functions work together.
The term operating memory predates MorpheusOS. Here it describes a practical business requirement: keeping enough reliable context for repeated work to improve. The test is visible in the next run — what did retained knowledge help the team do differently?
Common questions
What is the difference between retrieval and operating memory?
Retrieval finds relevant material. Operating memory retains the state around the work, including decisions, approvals, assumptions, unresolved risks and what should happen next.
Does operating memory replace systems of record?
Existing systems remain authoritative for their records. Morpheus carries the context, evidence and judgment around work across those systems.
What makes retained information trustworthy?
Its source, time, confidence, review status, scope and relationship to later corrections make the information understandable and reviewable.