remember

To save session findings as durable project knowledge, you must classify each discovered item by longevity and route it to the correct long-term memory surface, such as project memory or durable agent documents. This prevents reusable context from being lost in chat history.

Organizing working context and project documentation requires classifying findings by durability and validity, then writing or updating only the appropriate memory surface. This routing approach keeps short-lived working notes separate from durable project facts.

Managing documentation hygiene involves gathering relevant findings, classifying items to identify duplicates or conflicts, and updating only the correct store. It explicitly surfaces stale entries and conflicts that should be cleaned up to maintain reliable storage.

Yes, you can route operator instructions and convention documents to specific memory surfaces. The process classifies these items by durability and writes them to appropriate destinations like Docs, AGENTS, or Claude files instead of leaving them in chat history.

For unverifiable claims or conflicting context discovered during a work session, you should mark the uncertainty instead of storing them as facts. The process explicitly surfaces duplicates and conflicts, reporting what was stored alongside items that require cleanup.