File-based memory

File-based memory stores state in Markdown, JSON, or similar artifacts. It is portable and easy to edit directly, but integrity guarantees are manual.

Typical implementations append notes or overwrite JSON blobs. Without a deterministic reducer and observation lineage, teams rely on ad-hoc conventions for conflict handling.

{
  "contact": "Ana Rivera",
  "city": "Barcelona"
}

# Later overwrite
{
  "contact": "Ana Rivera",
  "city": "San Francisco"
}

This model can work for lightweight workflows but usually fails deterministic guarantees at scale. See platform memory, deterministic memory, schema constraints, and memory model comparison.