memory-manager

Cross-session memory for Marvin works by storing architectural choices, error patterns, and project conventions in structured files with YAML frontmatter. This enables proactive recall of past knowledge, ensuring continuity and learning across development sessions.

Logging architectural decisions and rejected alternatives requires a structured, file-based system with typed subdirectories and YAML frontmatter. By recording choices with confidence scores, this tiered memory architecture ensures past decisions are recalled and applied in future tasks.

Yes, proactive recall of project-specific conventions and error patterns is supported through a tiered memory architecture. It uses typed subdirectories and YAML frontmatter for efficient querying, maintaining an up-to-date understanding of project structure and conventions.

Maintaining a knowledge map of project structure and conventions involves storing and retrieving project knowledge in a structured, file-based system. This ensures Marvin maintains an up-to-date understanding of your project, facilitating continuity and learning across development sessions.

Yes, using file-based YAML frontmatter to store cross-session project knowledge is supported. It organizes decisions, error patterns, and project conventions in typed subdirectories, enabling efficient querying and proactive recall across different development sessions.

Marvin forgets architectural decisions between sessions because it lacks a persistent cross-session memory system. Without a structured, file-based memory architecture with typed subdirectories, past decisions, error patterns, and project knowledge are not retained or recalled.