Vault Recap

When to Activate

• Scheduled nightly via CRON.md
• User runs /ops-vault-recap
• After intensive work sessions

Purpose

1. Consolidate scattered session notes into proper vault locations
2. Validate vault structure integrity
3. Report and fix structural violations

Steps

Step 1: Scan Session Memory

bash
1Glob vault/memory/**/*.md       # All session notes

Read each file. Identify entries that should be promoted to vault sections:

Step 2: Recap & Consolidate

For each promotable entry:

1. Extract key information (decisions, insights, references)
2. Check if destination file already exists (append vs create)
3. Write to proper vault location following pattern-knowledge.md format
4. Respect vault naming: ###-name.md with frontmatter (name, type)

Step 3: Validate Structure

Run structural checks on all vault files:

Step 4: Fix Structural Issues

Auto-fixable (safe):

• Missing frontmatter → add with inferred name and type
• Wrong file prefix → rename to match ###- pattern

Report only (needs user):

• Depth violations (moving files changes references)
• Duplicate content across locations
• Orphaned files with no clear destination

Step 5: Clean Stale Memory

Session notes older than 7 days that have been fully recapped:

• Move to vault/05-Archive/ (not delete)
• Log what was archived

Step 6: Generate Report

yaml
1vault_recap:
2  timestamp: "{ISO date}"
3  memory_scanned: {count}
4  promoted: {count}
5  structure_checks:
6    total: {count}
7    passed: {count}
8    auto_fixed: {count}
9    needs_user: {count}
10  archived: {count}
11  issues:
12    - type: "{structural | duplicate | orphan}"
13      path: "{file path}"
14      detail: "{description}"
15      action: "{fixed | needs_user}"

Notes

• Never deletes vault files (archive instead)
• Respects validate-vault.sh rules as source of truth
• Memory files under vault/memory/ skip strict naming checks (per hook)
• Idempotent: recapping already-promoted content is a no-op