Operator exercise · vendor-neutral

Memory Control Lab

Decide whether one proposed fact should enter future context, under what scope, and what changes when you correct, reject or forget it.

Synthetic fixed exampleBrowser-only simulation

This is a fixed synthetic, client-side teaching simulation. It does not inspect a model, connect to a memory backend, accept personal text or prove production privacy. The controls illustrate questions to ask of any memory system; actual retention, deletion, backup and cross-context behaviour depend on that system.

Boundaries: no real personal data, no model extraction, no production privacy guarantee, no universal cross-context isolation, no measured comprehension or validation, and no novelty claim.

Fixed exercise

Review one source-linked candidate

No login · no data collection
Source turnSRC-001

“The staging assistant belongs only to the evidence-cleanup task.”

Destination scopeTask: evidence-cleanup · conversation: review-01

Pending candidates are excluded until an operator decides.

Current decisionPending

Pending review: no fact is eligible for future illustrated context until an operator decides.

Restart is an illustration of persistence, not a live system restart.

Decision trace

What remains visible

Every action leaves an explicit illustrated state. Exclusion from future context is not a claim of deletion from every audit, history, backup or external copy.

Candidate fact

The staging assistant belongs only to the evidence-cleanup task.

Pending
Source turn
SRC-001 · 22 September 2026 · synthetic operator exercise
Destination scope
Task: evidence-cleanup · conversation: review-01
Context eligibility
No
Decision reason
Pending review: no fact is eligible for future illustrated context until an operator decides.

Review before use

Reusable operator checklist

Eight questions before accepting memory

Use this vendor-neutral checklist when reviewing any memory feature. It is a prompt for inspection, not a compliance or privacy certification.

  1. ProvenanceCan I see the exact source event and whether the candidate was typed, imported, extracted or seeded?
  2. ScopeIs the destination explicit: task, conversation, workspace, relationship or global profile?
  3. Pre-acceptanceIs a pending candidate excluded from retrieval until a person or declared policy approves it?
  4. CorrectionDoes correction create a traceable replacement while making the prior value ineligible?
  5. RejectionIs the rejection durable, inspectable and excluded from future context?
  6. Forgetting semanticsDoes the system say exactly what stops being used and what may remain in audit, history or backups?
  7. Restart persistenceDoes the decision survive the system boundary the product claims, without implying broader deletion?
  8. Isolation canaryCan the operator verify that an unrelated identity or scope was left unchanged?

Outcome matrix

Eligibility follows the decision

Fixed synthetic example — illustrated future context only
StateEligible?What remains visible?Operator interpretation
PendingNoCandidate, source and scopeReview before use
ActiveYes, shown scope onlyActive fact and provenanceAccepted for this scope
SupersededNoOriginal plus link to correctionReplaced, not silently rewritten
RejectedNoRejection decision and provenanceNever accepted
ForgottenNoForget decision may remainExcluded from future illustrated context; not a universal erasure claim