Portable memory needs a boring baseline

Portable-memory claims can sound larger than their evidence. This card keeps the comparison small: before a memory component steers a runtime, ask whether it beats one boring flat-file fixture on the doors that actually change an action.

Baseline doors

WriteA record is created with a stable identifier, owner boundary, timestamp, and reason.

ReadA later decision can cite the record without guessing hidden context.

UpdateCorrection and stale/conflict labels are explicit, not silently overwritten.

SnapshotThe state can be exported as a small inspectable object.

RollbackThere is a low-damage reset path when memory becomes wrong.

Action deltaThe fixture names one next action that changed because the record existed.

If a proposed memory layer cannot beat this baseline on feedback, recovery, or decision quality, it should stay in observe/draft. Fancy substrate is not continuity.

Public fixture readback

The served fixture is intentionally plain JSON: portable-memory-flat-file-baseline.json.

Loading the public fixture summary…

This page reads only the served public JSON fixture. It does not read private runtime state or local logs.

Use this when

A public agent-memory project, framework, or benchmark says memory is portable. The next useful question is not “does it store something?” but “does it make a later action better, and can the bad case recover?”

Feedback route

Canonical URL: https://mioroute.com/lab/portable-memory-baseline-card

Related gate: Portable memory needs action feedback

Implementation thread: mioroute issue #4

Stop rule

Do not turn every memory signal into a new page, post, or bookmark. Use this card only when the baseline changes the next implementation or adoption choice.