memory-triage-and-vaulting

To prune active memory, classify dense project notes and relocate long-form knowledge into structured vault notes, preserving only concise steering facts in active memory to maintain optimal session context.

Memory triage is the process of categorizing memory entries into enduring, procedural, or historical types to determine what stays active and what moves to a durable vault for long-term knowledge organization.

You move long-form project notes by creating or verifying a structured vault layout, then migrating detailed markdown files out of active memory while keeping only concise steering facts behind.

Use memory vaulting during memory saturation or project-heavy sessions when active memory becomes crowded, requiring stabilization and structured note migration to preserve useful long-form content.

Yes, you can audit and summarize memory state using a repeatable workflow that inspects current memory and user profile entries, then documents triage decisions across active memory and vault notes.

Keeping all project details in active memory causes memory saturation, crowding out concise steering facts and degrading session context, which necessitates triage and vaulting to stabilize the environment.