BIG BRAIN Memory Bank

The Memory Bank is the heart of the BIG BRAIN system - it provides structured persistence of knowledge across memory resets, ensuring continuity and consistency in operations.

What is the Memory Bank?

The Memory Bank is a specialized documentation system designed to maintain perfect recall across complete memory resets. Unlike traditional documentation that serves as a reference, the Memory Bank is designed as a primary operational dependency - the system cannot function without it.

Key Principles

• Complete Documentation: Every aspect of the project must be documented
• Clear Structure: Information is organized in a predictable, consistent hierarchy
• Contextual Integration: Related information is linked and cross-referenced
• Progressive Detail: Information flows from high-level concepts to implementation details
• Verification Mechanisms: Built-in systems to validate the integrity of stored information

Memory Bank Structure

The Memory Bank follows a carefully designed structure:

memory-bank/
├── core/
│   ├── active/       # Currently relevant information
│   │   ├── projectbrief.md
│   │   ├── productContext.md
│   │   ├── activeContext.md
│   │   ├── systemPatterns.md
│   │   ├── techContext.md
│   │   └── progress.md
│   ├── foundation/   # Foundational project information
│   └── reference/    # Stable reference material
├── short-term/       # Temporary or transitional information
└── long-term/        # Historical or archived information

Core Files

The Memory Bank core files are the essential documents required for operation:

projectbrief.md

Foundation document defining core requirements and project goals

High Priority

productContext.md

Explains why the project exists, problems it solves, and user experience goals

High Priority

activeContext.md

Documents current work focus, recent changes, and immediate next steps

Critical Priority

systemPatterns.md

Outlines system architecture, technical decisions, and component relationships

High Priority

techContext.md

Lists technologies, development setup, and technical constraints

Medium Priority

progress.md

Tracks what works, what's left to build, and known issues

High Priority

Memory States

The Memory Bank operates through multiple states:

1. Initialization State: When a new session begins
2. Active State: During normal operation
3. Preservation State: When preparing for a memory reset (Bedtime Protocol)
4. Reset State: When memory has been reset and needs to rebuild from the Memory Bank

Bedtime Protocol

The Bedtime Protocol is a critical process for preserving state before a memory reset:

1. Capture: All volatile state is documented
2. Update: Core files are updated with the latest information
3. Verification: Memory Bank integrity is checked
4. Preparation: Setup is made for the next initialization
5. Shutdown: Controlled end of the current session

Learn More

Explore these sections to learn more about the Memory Bank:

• Core Files - Detailed information about each core file
• Structure - Understanding the Memory Bank organization
• Memory States - How memory states work
• Bedtime Protocol - The preservation process