The Memory Control Plane
This is the Memory Control Plane: a compact guide for giving the Unwind Brain durable recall without allowing old context to become hidden authority. The operator sees pressure, queues, and receipts before memory is trusted or changed.
Memory without a control plane becomes hidden authority.
The Brain already had memory language. The control-plane pattern makes it operational: typed records, privacy levels, expiry, retrieval modes, metadata-only recent indexes, content-free health, retention previews, action queues, and reviewed mutation routes.
The theory is not "remember more." The theory is "make recall governable." A memory system that cannot show its workload becomes mysticism. A memory system that shows too much becomes surveillance. The control plane lives between those failures.
The operator should be able to ask: What is stale? What needs review? Which receipts are dirty? Which records are unresolved? The operator should not need to open the private body of the memory to answer those questions. Metadata before memory body is the first law.
The memory layer becomes a governed workload, not a vault.
The Memory Control Plane is made of six surfaces: capture, index, health, queue, mutation, and receipt. Capture records what may be remembered. The index exposes safe metadata. Health shows system pressure. Queues name work that needs review. Mutation applies approved changes. Receipts prove what happened.
This is how the Brain preserves continuity without turning yesterday's assumptions into law. It can see the shape of memory pressure before trusting the content of memory itself.
Capture plane
Memory enters through a typed packet with privacy level, retention intent, source context, and review posture.
Index plane
Recent, health, retention, and action-queue surfaces expose metadata, not stored memory content.
Queue plane
The system can name unresolved records, stale receipts, retention gaps, and repair candidates without mutating them.
Mutation plane
Resolution, retention repair, receipt hygiene, and content changes require reviewed requests and rollback notes.
Receipt plane
Every accepted mutation leaves a receipt that can be inspected later without exposing sensitive payload content.
The memory layer is an immune boundary, not just a database.
In the organism model, memory is where continuity becomes risk. Good memory gives the Brain identity, context, and better judgment. Bad memory turns old assumptions into invisible law. That is why every record must carry type, privacy, retention, receipt, and review posture.
The laws are intentionally plain: no sensitive content by default. Metadata before memory body. Retention is an active decision. No mutation without a receipt. Repair requires approval. Old memory is evidence, not current truth, until health and retention checks pass.
The control plane is the organ that lets the creator see systemic pressure without collapsing into content review. It says, "these records need triage," not "here is every private thought." It says, "this mutation needs approval," not "the system already repaired itself."
Control surfaces
Authority split
Build memory as an approval path from capture to receipt.
Start with a typed memory record. Add privacy level, retention window, source, confidence, and review status. Expose recent and health views as metadata-only surfaces. Route pressure into queues. Prepare mutation packets with reason, expected change, retention impact, and rollback note. Apply only after review, then append a receipt.
This recipe makes memory inspectable without making it naked. The Brain can recommend the next queue, but it cannot quietly rewrite what it remembers.
The control plane refuses to confuse visibility with permission.
How the Brain should use this control plane.
The Brain should treat memory as a governed workload, not a hidden oracle. It can prepare summaries of queue pressure, recommend which repair path needs review, and generate a mutation packet. It must not silently edit memory, expose stored content, or treat an old record as current truth without receipt and retention checks.
Inspect pressure
Use recent, health, retention, and queue views to understand the workload without reading private content.
Prepare a reviewed packet
When repair or write is needed, build a packet with memory id, reason, expected mutation, retention impact, and rollback note.
Wait for authority
The system can recommend the next action, but mutation happens only after explicit creator approval or a reviewed internal gate.
Record next-cell memory
The next cell should connect this control plane to public grounding, so answer drafts can cite current memory status without exposing private content.
The memory layer now has hands it refuses to move by itself.
Proof ledger: the page, metadata, registry summary, tests, build, and local smoke must agree before this becomes production truth. The posting assets for this transmission remain internal creator material, not public documentation.
All Transmissions→