Memory Map
Verified August 12, 2026

Mike's Memory Stack: Keep, Fix, or Cancel?

A plain-English map of what you own, why each layer exists, what actually returned memory, and what should stop costing attention or money.

Start exploring ↓
UnderstandConnectApply
The answerFour layers, not fourteen products

Archive → Canonical Brain → MEMZ → Hindsight

Archive → Canonical Brain → MEMZ → Hindsight

Raw history stays safe. Master Brain is the source of truth. MEMZ chooses the right read path. Local Hindsight holds only curated, high-value runtime memories.

  • master_knowledge_v2 is canonical.
  • Hindsight is the local episodic cache.
  • QMD and LanceDB are local search sidecars.
Do not bulk-restore 1.16M facts into active Hindsight.
KeepThese systems have unique jobs

Keep the spine and the recovery layers

Keep the spine and the recovery layers

The historical Hindsight evacuation, QMD, Pieces, Cloud Mem, LanceDB, Master Brain, MEMZ Supabase, and local Hindsight all provide distinct value when their authority is clearly limited.

  • Archive: 1,163,333 Hindsight facts, checksummed.
  • Cloud Mem: 13,642 observations and 101,819 vectors.
  • LanceDB: 49,987-row offline mirror.
  • Pieces: recent desktop workstream context.
FixHealthy is not the same as useful

Repair retrieval, identity, and provenance

Repair retrieval, identity, and provenance

Graphiti answers health checks but not searches. Honcho authenticates but has no proven Mike memory mapping. Hindsight works locally, but only 4,096 facts are active and need source references back to the archive and Master Brain.

  • Graphiti: make one real search pass or park it.
  • Honcho: map Mike → workspace → peer → session.
  • Hindsight: retrieve archive facts on demand, never bulk load.
Pause or cancelRedundant hosted mirrors

Stop paying for memory that owns no unique job

Stop paying for memory that owns no unique job

Mem0 and Supermemory returned data, but they duplicate personal and episodic recall already covered by Master Brain and local Hindsight. Zep is useful only if you can name temporal relationship questions that flat retrieval cannot answer.

  • Mem0: preserve 1,968 records, then stop new writes.
  • Supermemory: export, reconcile, then cancel if no runtime depends on it.
  • Zep: keep only as the single graph product.
  • Never run duplicate fan-out writes by default.
DecisionThe smallest useful operating queue

Prove one job per backend

Prove one job per backend

Preserve before retirement. Repair reads before adding data. Make MEMZ the one front door, Master Brain the authority, and local Hindsight the bounded runtime cache.

  • 1. Freeze and inventory all hosted mirrors.
  • 2. Repair Graphiti and Honcho reads or retire them.
  • 3. Add archive-on-demand retrieval with provenance.
  • 4. Cancel every backend without a unique passing job.
No restore, ingest, or paid embedding without explicit GO.