Design a Memory Index Loaded Every Session

About this workflow

Build the pattern behind minimalist memory systems: a compact index file the agent always loads, pointing to detail files it loads on demand.

What happens when you run it

1. 1
   The index is a map; the details are the territory.

   Runs flow-design-memory-index-every-session-1-structure-the-index-and-details on Claude Sonnet 4.6
2. 2
   Constant context cost with reach into everything.

   Runs flow-design-memory-index-every-session-2-wire-loading-index-always-details-on-de on Claude Sonnet 4.6
3. 3
   An index that drifts from reality is worse than no index.

   Runs flow-design-memory-index-every-session-3-maintain-the-index-as-memory-evolves on Claude Sonnet 4.6

Best for

• •Recurring tasks you currently copy-paste between tools.
• •When a single prompt isn't enough — you need a chain where output(n) feeds prompt(n+1).
• •Fork and adapt if your inputs differ materially from the author's use case.

Models used