Module 3 · Lesson 12 – Building a Real Memory Stack

One source of truth, maintained under pressure

The One Source of Truth Rule

Memory stacks fail when fragmented. If your decisions live in:

• Multiple docs across different tools
• "The latest chat history"
• Email threads and Slack messages
• Your head ("I'll remember this")

Then you do not have a memory stack. You have chaos.

One source of truth. One document. One system. When you need context, you go there. If it's not in your stack, it does not exist.

Stack Format (Mandatory)

Every entry in your memory stack must include all four fields:

Session: What problem you were solving (specific, not generic)
Date: When the decision was made
Decision: What you're executing, not considering (actions, not possibilities)
Usage: When you'll need this again (triggers re-injection)

Example Stack Entry:

Session: Customer Acquisition Strategy - Cold Email
Date: 2026-03-08
Decision: Send 50 cold emails/week to SaaS CTOs using 3-line format (problem/solution/CTA), A/B test subject lines, track reply rate in spreadsheet, minimum 6% reply rate to continue
Usage: Re-inject every Monday when planning weekly outreach; re-inject when reporting results to stakeholders

What Earns Storage

Do NOT store:

• Drafts or explorations
• Ideas you're "considering"
• Speculation or possibilities
• AI output you haven't acted on

ONLY store:

• Final decisions
• Hard rules and constraints
• Non-negotiables proven by execution
• Lessons from real failures

Memory is not a scrapbook. It's a control system.

Maintenance Routine

Memory stacks decay without active maintenance:

Weekly Review (5-10 minutes):

• Add new stack entries from this week's sessions
• Mark entries that were actually used this week
• Flag entries that might be stale

Monthly Pruning (15-20 minutes):

• Remove entries that haven't been used in 60 days
• Update entries where decisions changed
• Consolidate redundant entries

Quarterly Reset (30-45 minutes):

• Archive entire stack with date
• Rebuild from scratch with only actively-used entries
• This prevents stack bloat and forces verification

The 10-Second Test

If you can't find a decision in your stack within 10 seconds, you never documented it properly. Your stack should be:

• Searchable (Cmd+F or Ctrl+F works instantly)
• Chronologically organized (newest first)
• Clearly labeled with session names that match how you think about problems

Common Failure Modes

"I'll start documenting next week" — No. Start now or accept drift.

"I'll remember this one" — You won't. Document or lose it.

"This decision is too small to document" — If it matters enough to decide, it matters enough to record.

"My stack is getting too long" — Prune it. Quarterly reset exists for this reason.