From 57130ccfbcea7f680dcb102fad6b6f8a81baeb32 Mon Sep 17 00:00:00 2001
From: Antoine <antoine.letarte@gmail.com>
Date: Thu, 12 Feb 2026 14:20:57 +0000
Subject: [PATCH] docs: add nightly memory digestion methodology

---
 docs/NIGHTLY-MEMORY-METHODOLOGY.md | 73 ++++++++++++++++++++++++++++++
 1 file changed, 73 insertions(+)
 create mode 100644 docs/NIGHTLY-MEMORY-METHODOLOGY.md

diff --git a/docs/NIGHTLY-MEMORY-METHODOLOGY.md b/docs/NIGHTLY-MEMORY-METHODOLOGY.md
new file mode 100644
index 00000000..770bc616
--- /dev/null
+++ b/docs/NIGHTLY-MEMORY-METHODOLOGY.md
@@ -0,0 +1,73 @@
+---
+tags:
+  - Project/Atomizer
+  - Protocols
+  - Memory
+status: active
+date: 2026-02-12
+---
+
+# Nightly Memory Methodology — “Restore → Sort → Dream → Resolve”
+
+## Purpose
+Run a consistent nightly process to:
+- capture the day’s key work and decisions
+- distill durable memory (preferences, protocols, decisions, project state)
+- convert open loops into explicit next actions
+- reduce noise + avoid memory rot
+
+This is intended to be executed automatically by the Manager agent via a scheduled cron job.
+
+## Schedule
+- **Runs nightly at 00:00 America/Toronto** (midnight Toronto time).
+- **Delivery target:** Slack `#all-atomizer-hq`.
+
+## Inputs
+1. Today’s key Slack threads/DMs (decisions, blockers, requests, promises)
+2. Work artifacts created/changed (docs, outputs)
+3. Open tasks + what actually got done
+
+## Pipeline
+
+### 1) RESTORE (capture raw truth)
+Capture a compact factual timeline of the day.
+- Extract: decisions, assumptions, constraints, blockers, open questions, promises made.
+- Write/update: `memory/YYYY-MM-DD.md`.
+
+### 2) SORT (route to the right home)
+Promote only what should persist.
+
+**Routing rules**
+- Stable preferences / operating rules → `MEMORY.md` (or `memory/prefs.md` if split later)
+- Project state (status/next steps/blockers) → `memory/projects/<project>.md`
+- Decisions + rationale → `context-docs/04-DECISION-LOG.md`
+- Protocol/process improvements → appropriate docs (or a protocol doc)
+- Ephemera / FYI → do not promote (optionally keep minimal note in daily file)
+
+### 3) DREAM (synthesize + improve)
+Generate a small set of compounding improvements (3–10):
+- process/protocol improvements
+- reusable templates/checklists
+- automation opportunities
+- risks to track
+
+Write these as: **“Dreams (proposals)”** in `memory/YYYY-MM-DD.md`.
+
+### 4) RESOLVE (turn dreams into action)
+- Convert accepted items into tasks with: owner + next action.
+- File tasks into the relevant project memory.
+- Flag CEO sign-offs explicitly:
+  - **⚠️ Needs CEO approval:** <decision> + recommendation
+
+## Nightly Outputs
+1. Updated `memory/YYYY-MM-DD.md`
+2. Updated project memories + decision log (only when warranted)
+3. A short post to Slack `#all-atomizer-hq`:
+   - “Tonight’s digestion” summary
+   - “Tomorrow brief” (5–10 bullets: priorities, blockers, asks)
+
+## Quality Gates (anti-rot)
+- Avoid duplication; prefer canonical docs and link/reference when possible.
+- Never store credentials/tokens.
+- If uncertain, mark **unconfirmed** (do not assert as fact).
+- Keep “daily note” factual; keep “dreams” clearly labeled.