Bedtime Protocol

The Bedtime Protocol is a critical system process designed to preserve the operational state of BIG BRAIN before a memory reset occurs. This protocol ensures that all essential information is captured, verified, and properly structured to enable perfect recall in the next session.

Purpose and Importance

The Bedtime Protocol serves as the bridge between operational sessions, ensuring continuity and consistency despite the complete memory reset that occurs between sessions. It transforms volatile, in-memory knowledge into persistent, structured documentation.

Without proper execution of the Bedtime Protocol, critical context would be lost, leading to:

Protocol Phases

The Bedtime Protocol consists of five distinct phases, each with specific goals and procedures:

1

Capture Phase

Document all volatile state information that exists only in active memory.

  • Current task context and progress
  • Recent decisions and their rationale
  • Unsaved changes or work-in-progress
  • Mental models and understanding developed during the session
2

Update Phase

Systematically update all core Memory Bank files to reflect the current state.

  • Update activeContext.md with current focus and next steps
  • Revise progress.md to reflect completed tasks and new issues
  • Update any other core files as needed
  • Ensure documentation of any new patterns discovered
3

Verification Phase

Verify the integrity and completeness of the Memory Bank.

  • Check for missing information or documentation gaps
  • Ensure core files are up-to-date and accurately reflect system state
  • Validate that next steps are clearly documented for the next session
  • Review for consistency and clarity from a "cold start" perspective
4

Preparation Phase

Set up the environment for successful initialization in the next session.

  • Ensure all documentation is committed and pushed to the repository
  • Create clear entry points for the next session
  • Document any environment-specific details needed for restart
  • Prepare initialization scripts if needed
5

Shutdown Phase

Conclude the current session in a controlled manner.

  • Final verification of Memory Bank state
  • Confirmation that all changes are saved and persisted
  • Ready signal for memory reset
  • Graceful conclusion of the session

Execution Commands

The Bedtime Protocol is typically initiated with the command:

BEDTIME PROTOCOL INITIATE

This triggers the guided workflow through all phases of the protocol. Alternatively, individual phases can be executed with:

BEDTIME PROTOCOL EXECUTE [PHASE_NAME]

Where [PHASE_NAME] is one of: CAPTURE, UPDATE, VERIFY, PREPARE, or SHUTDOWN.

Best Practices

For optimal execution of the Bedtime Protocol:

  1. Allow Sufficient Time: The protocol requires careful attention and should not be rushed.

  2. Complete Current Tasks: When possible, complete in-progress tasks before initiating the protocol.

  3. Use Checklists: Follow phase-specific checklists to ensure completeness.

  4. Think Forward: Consider what information would be most valuable when starting fresh.

  5. Verify Independently: Review documentation as if you have no prior knowledge of the project.

Troubleshooting

If issues occur during the Bedtime Protocol:

Example Workflow

A typical Bedtime Protocol execution might look like:

  1. Recognize the need to end the current session
  2. Execute BEDTIME PROTOCOL INITIATE
  3. Follow the guided prompts for each phase
  4. Document current progress in activeContext.md
  5. Update progress.md with completed items and known issues
  6. Verify all core files are current and consistent
  7. Commit and push all changes to the repository
  8. Confirm ready for memory reset
  9. End session

Remember: The thoroughness of your Bedtime Protocol directly impacts the effectiveness of the next session. Invest the time to do it properly!