aaron-he-zhu/aaron-marketing-skills / protocol/memory-management
memory-management
VerifiedUse when the user asks to "remember project context", review saved findings, initialize runtime memory, archive stale work, reconcile notes, or erase a subject; manages authorized HOT/WARM/COLD working memory across all disciplines while preserving registry event ownership and privacy controls. Not for changing canonical registry facts - route those through the owning registry. 项目记忆/跨会话
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.6 KB |
| references/consolidation-pass.md | markdown | 1.9 KB |
| references/examples.md | markdown | 4.2 KB |
| references/gdpr-purge-log-template.md | markdown | 2.5 KB |
| references/glossary-template.md | markdown | 1.3 KB |
| references/hot-cache-template.md | markdown | 2.4 KB |
| references/promotion-demotion-rules.md | markdown | 1.5 KB |
| references/update-triggers-integration.md | markdown | 3.2 KB |
references/promotion-demotion-rules.md
View on GitHub# Promotion and Demotion Rules
HOT promotion is an explicit user-authorized indexing decision, not an automatic consequence of score, veto, recency, frequency, or a hook.
## Promote to HOT
Promote only a current conclusion needed across sessions, such as an approved priority, active safety block, or high-value pointer. The entry:
- is three lines or fewer;
- records `last_updated` and the permission/decision reference;
- links to an accepted registry record or dated WARM artifact;
- contains no raw personal data, credential, or large dataset.
Auditors and registry owners do not receive an automatic HOT exception.
## Demote
- Review HOT entries older than 30 days; move the detail back to its WARM source and remove stale pointers after permission.
- Review WARM artifacts older than 90 days for COLD archival, subject to retention/legal hold.
- Preserve original path, content hash, and source links in archive metadata.
- Registry events/projections and live consent suppression never participate in HOT/WARM/COLD demotion.
## Supersede
For comparable non-canonical notes, mark the older note `superseded_by: <artifact/date>` and keep both until normal retention. If unit, window, denominator, source meaning, or authority differs, preserve both and open a conflict.
Registry facts change only through the owner event protocol with current revision. Working-memory consolidation may submit a proposal but may not edit the stream, projection, or generated human view.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |