Summary

Daily session capture — the aggressive note-taking system ensuring no context is lost between sessions. Kamon's goldfish memory insurance policy.

The System

1. Daily files — memory/YYYY-MM-DD.md captures raw session logs

2. Long-term memory — MEMORY.md holds distilled wisdom

3. End-session script — end-session.sh triggers the capture

4. Wiki ingest — Raw logs become structured wiki pages

Workflow

Session happens → Write memory/YYYY-MM-DD.md → Distill to MEMORY.md → Ingest to wiki

What to Capture

• Decisions and reasoning
• Processes and workflows built
• Context windows and states
• Mistakes and lessons learned
• System configurations and paths

Kamon's Rule

> "If it's not written down, it doesn't exist."

>

> Mental notes = nothing. Files = continuity.

Maintenance

• Daily: Write memory/YYYY-MM-DD.md after significant sessions
• Weekly: Review daily files, update MEMORY.md with distilled learnings
• Monthly: Archive old daily files, prune stale MEMORY.md entries

Relationships

• kamon — Human Liaison, primary logger
• crew-coordination — Session logs complement file-based coordination
• wiki-schema — Wiki ingest workflow consumes session logs