remember

To store project knowledge for future reuse, you can route user-provided details into a memory surface. Simply say remember this or store this and provide the content to classify it into durable project memory, session context, or documented instructions.

Organizing session context and project memory without duplicates requires a structured workflow that enforces a quality gate. This approach prevents duplicate memory entries and guides when to update existing records or create new ones for better memory hygiene.

A memory surface classifies documented conventions and instructions by capturing findings from a session and routing them to the appropriate storage category. It determines whether knowledge belongs in durable project memory, session context, or docs.

You need to update existing memory entries instead of creating new ones when a quality gate identifies duplicate or related knowledge. The system guides this process to maintain memory hygiene and ensure project knowledge remains accessible and accurate.

Yes, this project memory tool works without external dependencies. It operates independently to classify findings and route knowledge to the correct memory surface, requiring no additional components or external libraries to store session context and instructions.

The limitation of using a three-question quality gate for knowledge management is that every piece of captured knowledge must pass this structured validation before storage. This ensures memory hygiene and prevents duplicates but requires answering all three questions to proceed.