๐Ÿง 
Proposal โ€” May 12, 2026

Warren's New Memory Lifecycle

A narrated proposal for the team: what changed, why it matters, the trade-offs, and what we're asking for.

1 / 10
๐Ÿ†• Proposal โ€” Activated May 12, 2026
๐Ÿง 

Warren's New Memory Lifecycle

Three systems that turn daily operational noise into durable knowledge โ€” automatically, every night. Nothing changes without human approval.

Before: knowledge that drifts and decays

Every day, Warren logs directives from Tony, decisions with clients, dashboard rules from Joana, infrastructure changes, strategy shifts. Each day gets its own work journal. In a month, that's 50+ journals โ€” thousands of lines where standing rules are buried alongside debug logs and one-time fixes.

โŒ Before (through May 11)
  • 6,674 lines of raw journals โ€” noise competing with signal
  • 776 search chunks โ€” duplicates and debug logs diluting results
  • Yesterday's journal loaded raw: 245 lines of play-by-play into context
  • MEMORY.md stale since April 11 โ€” 31 days of knowledge not consolidated
  • Directives from Tony forgotten between sessions โ€” "noted" โ‰  remembered
  • Search accuracy: score 0.477 โ€” nearly half the time, wrong chunk surfaces first
โœ… After (May 12)
  • 1,777 lines of compressed journals โ€” 73% reduction, pure signal
  • 493 search chunks โ€” 36% fewer, each denser in keywords
  • Yesterday's journal compressed: 57 lines of distilled checkpoint
  • MEMORY.md current โ€” 89 lines, 11 durable facts promoted, Victor-approved
  • Every directive persisted and consolidated โ€” "noted" = written to disk
  • Search accuracy: score 0.710 โ€” 49% improvement on same query

Three systems, activated today

Each solves a different part of the knowledge decay problem. All run at 03:00 PT every night. None alter canonical memory without human approval.

73%
Journal lines reduced
11
Durable facts promoted
493
Optimized search chunks
+49%
Search accuracy gain
๐Ÿ“‹

1. Nightly Consolidation

Reads daily journals, classifies each entry as durable or transient, proposes updates to MEMORY.md. Human reviews and approves before anything changes.

๐Ÿ—œ๏ธ

2. Journal Compression

Compresses yesterday's raw journal into a dense checkpoint. Same file, fewer lines, better signal. Original preserved in git. Runs automatically after consolidation.

๐Ÿ’ญ

3. Dreaming

Scans what Warren kept searching for across sessions. Surfaces patterns nobody explicitly wrote down. Writes to its own diary โ€” never alters MEMORY.md.

Cost impact and what we're proposing

The systems activated today cost nothing extra. We're proposing one additional upgrade: better embedding model for search accuracy โ€” enabled by the compression savings.

ComponentBeforeAfterMonthly Cost
Nightly ConsolidationManual / neverAutomatic, propose-only$0 (uses existing cron)
Journal CompressionN/A1 API call/night~$0.15/night โ†’ $4.50/mo
DreamingDisabledEnabled, conservative$0 (gateway internal)
Embedding: 3-small โ†’ 3-large$0.07/mo (776 chunks)$0.26/mo (493 chunks)+$0.19/mo
Total additional costโ€”โ€”~$5/month
โš ๏ธ Trade-offs accepted
  • Original journal detail lost from search index โ€” compressed version is denser but loses nuance (quotes, debug context). Git preserves originals.
  • Embedding vectorScore slightly lower per chunk (0.681 โ†’ 0.597) โ€” but compensated by BM25 textScore jumping (0 โ†’ 0.976). Net: +49%.
  • Compression quality depends on LLM โ€” using gpt-4.1-mini. May miss context in rare edge cases. Non-fatal: original always in git.
โœ… What we gain
  • 36% fewer search chunks โ€” less noise, better results
  • 73% less context loaded from yesterday โ€” model focuses on signal
  • Standing rules never forgotten โ€” consolidated into always-loaded MEMORY.md
  • Audit trail complete โ€” every compression and consolidation has a git commit
  • Human gate preserved โ€” consolidation proposes, never promotes alone

Nightly Consolidation

Reads what was written. Proposes what to keep. Never decides alone.

โฐ Cron fires at 03:00 PT

Spawns an isolated session. Reads every daily journal since last distillation.

Automatic

๐Ÿ“– Classify every entry

DURABLE (cross-session fact) ยท TRANSIENT (resolved) ยท TOPIC (belongs in specialized file) ยท SUPERSEDES (updates existing)

Automatic

โœ๏ธ Write MEMORY.md.proposed

Creates proposed file + safety archive. Validates line count, pointers, idempotency. Does not touch MEMORY.md.

Automatic

๐Ÿ”’ Human Review Gate

Operator reviews line by line. Nothing promoted until explicit "approved."

Human approval required

๐Ÿ—œ๏ธ Compress yesterday's journal

Raw journal โ†’ dense checkpoint in-place. Original in git. Search index re-processes automatically.

Automatic

Dreaming

Reads what was repeatedly searched for. Surfaces patterns nobody explicitly wrote down.

โฐ Gateway cron at 03:00 PT

Memory plugin scans the recall store โ€” every search query and fact retrieval from the past 30 days.

Automatic

๐ŸŽ›๏ธ Significance filter

Must pass all gates: accessed โ‰ฅ3 times, relevance โ‰ฅ0.8, โ‰ฅ3 unique queries. Recent facts weighted higher (14-day half-life).

Conservative defaults

๐Ÿ““ Write to dream diary

Patterns go to memory/.dreams/. Does not alter MEMORY.md or daily files. Read-only output for operator review.

Read-only output

Three layers of memory

Each layer has different reliability. The lifecycle moves important facts up the stack.

๐ŸŸข

Layer 1 โ€” Always loaded (100%)

MEMORY.md: 89 lines of standing rules, client registry, infrastructure facts, strategy. Loaded in every session, no search needed. This is the target.

๐ŸŸฃ

Layer 2 โ€” Loaded by trigger

Topic files (active-pending.md, pipeline-knowledge.md). Load when the right context triggers. Precise when triggered correctly.

๐ŸŸก

Layer 3 โ€” Search-dependent

Compressed daily journals. Searched via embeddings + keywords. Now 493 dense chunks instead of 776 noisy ones. Better, but still probabilistic.

The consolidation moves facts up: Layer 3 โ†’ Layer 1. Important knowledge stops depending on search accuracy and becomes permanent context.

The compression improves Layer 3 itself: fewer, denser chunks = better search results when you do need to reach into history.

The dreaming detects what should move up: patterns Warren keeps searching for that nobody promoted yet.

What to expect

๐Ÿ“

Every morning

If there are new durable facts, a proposed file waits for review. If nothing changed, nothing proposed. No noise.

๐Ÿ”’

Nothing changes without you

Consolidation proposes, never promotes. MEMORY.md is never overwritten automatically. Any operator can approve.

๐Ÿ—œ๏ธ

Yesterday is always compressed

The raw journal from yesterday becomes a 20-60 line checkpoint overnight. Less context noise, better model attention.

๐Ÿ““

Dream diary builds up

Over weeks, patterns emerge: facts Warren keeps reaching for. Readable anytime at memory/.dreams/.

๐Ÿ”„

What Tony says persists

Directives, rules, terminology, strategy โ€” captured daily, then consolidated into permanent memory. "Noted" = written to disk.

๐Ÿ›ก๏ธ

Full audit trail

Every compression and consolidation gets a git commit. Every promotion gets an archive. Nothing is lost.

What we're asking the team to approve

Three items. Two are already active with zero cost. One requires a config change.

โœ…

Already active (no approval needed)

Nightly consolidation (propose-only mode) + journal compression + dreaming (conservative defaults). Cost: ~$4.50/month for compression API calls. Everything else: $0.

๐Ÿ”„

Proposed: Upgrade embedding model

Switch from text-embedding-3-small to text-embedding-3-large. Higher accuracy on search. Cost delta: +$0.19/month. Requires config change + re-index (one-time, ~30 seconds).

๐Ÿ—ณ๏ธ Total additional cost: ~$5/month

For 73% less noise in context, 49% better search accuracy, automated knowledge consolidation, and standing rules that never get forgotten.

Glossary

Durable
A fact true across sessions โ€” standing rules, team info, architectural decisions. Lives in MEMORY.md (Layer 1).
Transient
Session-specific, resolved, or superseded. Debug logs, one-time fixes. Gets archived, not promoted.
Topic
Durable but too detailed for MEMORY.md. Lives in a specialized file loaded on-demand (Layer 2).
Supersedes
A new fact that contradicts or updates an existing entry. Old entry replaced, not duplicated.
Recall
A record of what Warren searched for during sessions. Logged with timestamp, score, and source.
Dream
A pattern surfaced from recall โ€” something repeatedly accessed but not written down yet.