Audit every profile's memory file weekly against written principles
One sub-profile per project, each with its own memory, and a weekly pass that checks each memory file against a written rule of what belongs there.
The weekly memory cleanup goes through each memory file to audit it against our 'principles of what belongs into each profile's memory'
— @ogiberstein, 2026-04-21, via the public Nous Discord archive.
The contributor runs a main agent plus one sub-profile per project, each keeping its own memory file. Memory still accumulates stray entries, so a scheduled weekly cleanup reads every memory file and audits it against a written statement of what belongs in each profile's memory, pruning the rest so the main agent's memory stays high-level and each project's stays specific.
Limitations: A process the author runs, described in outline; the source does not include the principles document or the audit prompt. Memory files have a size cap, and what counts as belonging is the author's judgement, not a measured rule.
Documentation check: this specific community technique was not found in the official English reference snapshot (1f2b9e0) or the cached prompt guides. Related built-in features are documented. This is a bounded source review, not a claim about every document or independent execution testing.