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/gdpr-purge-log-template.md
View on GitHub---
name: gdpr-purge-log-template
description: Honest, minimal schema for memory/privacy/erasure-log.md entries — a human-readable record of erasure requests, not an auditor artifact or erasure proof.
type: reference
---
# Erasure Operation Log — `memory/privacy/erasure-log.md`
An append-only, human-readable record of every Art 17 / CCPA §1798.105 erasure request
handled by `memory-management`. It documents **what was requested and what the working tree
edit did** — it is NOT a cryptographic or audit-grade proof of complete erasure.
`memory/audits/` is reserved for the eight typed marketing gate artifacts. Privacy operations are
operational records with a different construct and therefore never share that namespace.
> **Read this first — scope honesty.** A purge edits the **working tree** only. If `memory/` is
> under version control, the subject still exists in git history; verify with
> `git log -S"<name>" -- memory/` and use `git filter-repo` for true history erasure (the user's
> responsibility, out of scope here). This log does not, and cannot, prove that the subject is gone
> everywhere. Do not present it as such to a data subject or auditor. There is no salted-fingerprint
> or reingest-blocking mechanism in the hooks; do not record fields that imply one exists.
## Entry schema
Append-only YAML list, newest at the bottom. One entry per purge. **Never store the raw subject** —
use a stable redacted label.
```yaml
- date: 2026-06-10 # date the purge was run
redacted_label: "Subject-A1B2" # stable non-identifying label; NEVER the raw name
legal_basis: art_17_request # art_17_request | ccpa_1798.105 | proactive_minimization
action: anonymize # delete | anonymize
scope: # working-tree files edited
- memory/hot-cache.md
- memory/entities/acme-corp.md
files_modified: 9 # how many files were changed
working_tree_only: true # always true — git history is NOT touched by this flow
note: "Replaced subject string with [REDACTED] across 14 lines. Advised user to run git filter-repo for history."
```
## Required fields
`date`, `redacted_label` (never raw), `legal_basis`, `action`, `scope`, `working_tree_only: true`.
Everything else is optional context. Keep `note` free of the raw subject name.
## Cross-references
- [memory-management SKILL.md §GDPR / Privacy Compliance](../SKILL.md) — purge procedure and its honest limitation
- [references/skill-contract.md](../../../references/skill-contract.md) — Write Paths table
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 |