memory-management Checked

Stop and ask when a persistent write has not been authorized, a purge match is ambiguous, a new fact conflicts with a user-approved decision or accepted registry record, a natural-person lawful basis is missing, or a requested delete could affect unrelated records.

Proceed without a new question only for read-only lookup, verification, dry-run planning, or an operation already covered by explicit authorization in the current request. Never treat routine archival, an auditor veto, or a hook trigger as write permission.

Instructions

### Runtime Reads

• ../../references/runtime-invocation.md

### 1. Initialize

1. Copy the minimal safe starters from memory/templates/ into runtime memory/ only after authorization.

2. Read runtime-invocation.md (../../references/runtime-invocation.md), resolve AARON_SKILLS_ROOT="${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || true)}", verify the registry script/event schema/system catalog, then run python3 "$AARON_SKILLS_ROOT/scripts/registry-events.py" init to create private event/projection directories with restrictive permissions. A standalone one-folder install cannot initialize or claim registry state.

3. Confirm .gitignore excludes runtime memory and git status --ignored shows it as ignored.

4. Do not seed real names, contact data, credentials, or production exports into templates.

### 2. Query

1. Check live consent with python3 "$AARON_SKILLS_ROOT/scripts/registry-events.py" is-suppressed <aggregate-id> before any send-eligibility answer.

2. Query the relevant registry projection and record its last_offset/revision.

3. Read HOT as an index, then follow its evidence pointer into WARM or an accepted registry record.

4. Search COLD only when the user asks for historical context or active evidence is insufficient.

5. Label historical, stale, proxy, calculated, estimated, and user-provided facts explicitly.

Absence is Unknown. A missing note, profile, tool result, or projection field is never negative evidence and never silently becomes Partial.

### 3. Capture and Promote

• Save a dated WARM artifact only after permission. Include source refs, observation dates, assumptions, open loops, and the registry offsets read.
• Promote at most three lines to HOT when the user explicitly pins the conclusion. HOT contains a pointer and current summary, not raw evidence.
• Refresh memory/session-checkpoint.md after each completed skill handoff (template: memory/templates/session-checkpoint.md; cap 40 lines / 8 KB): chain visited set and depth, pending handoff, registry offsets read, pending proposal count, last gate verdict, and the one-line resume action. Clear it when no work is in flight. It is a resume hint for the SessionStart hook — never canonical truth, and offsets must be re-read from live projections before acting.
• Non-owner skills submit durable truth as operation: propose to the relevant event stream. They do not append free-form lines or edit projections.
• Only a host-capability registry-owner principal may accept/reject a proposal or issue an owner upsert/transition.
• memory/decisions.md entries require approved_by: user, an approval reference, and date. Inferred options belong in open loops, not approved decisions.

### 4. Demote and Archive

• HOT entries older than 30 days are candidates for demotion to their WARM source after review.
• WARM files older than 90 days by last_updated are candidates for COLD archival with a YYYY-MM-DD- prefix.
• Archive moves preserve content hash, original path, source pointers, and supersession metadata.
• Event streams and registry projections never enter HOT/WARM/COLD lifecycle operations. Do not rotate, truncate, compress, or relocate them through this skill.

### 5. Consolidate

1. Merge duplicate non-canonical notes only when they represent the same unit, field, observation window, and source meaning.

2. Preserve conflicts. Mark the older note superseded_by only when newer evidence is comparable and authority is equal or higher.

3. For registry-owned facts, create a proposal with current expected_revision; do not edit the view or event stream.

4. Flag orphan artifacts, broken Markdown links, nonexistent memory paths, unreferenced claims, and HOT conclusions without evidence pointers.

5. Keep append-only event history and proposal decisions intact. Consolidation never clears, consumes, or rewrites an event stream.

### 6. Audit Artifacts

Auditor outputs are written only after explicit authorization and must pass python3 "$AARON_SKILLS_ROOT/scripts/validate-audit-artifact.py" <artifact> --relative-path <artifact> after the verified runtime-root preflight. memory/audits/ is reserved for the eight typed gate sinks. memory-management may build a pointer-only monthly index at memory/indexes/audits/YYYY-MM.md; it must not copy or reinterpret scores into a new aggregate. Status describes execution, verdict describes gate findings, and the original framework/profile/version remain attached.

### 7. Privacy and Erasure

Use memory-management purge <pseudonymous-aggregate-id> only with explicit user or data-subject authority.

1. Run a dry search across HOT/WARM/COLD notes, rendered registry views, projections, exports, and indexes. Present exact matches without echoing unnecessary personal data.

2. Apply an immediate consent suppress event first when communications may be involved. Confirm suppression by replay, not by a cached view.

3. Delete or anonymize authorized working notes and rendered views. For each