Archive

Step 2: Archive Process

For each project to be archived:

1. Read the project file(s)

   • Get full content and metadata
   • Note any linked resources or assets

2. Move to archives:

   For Projects:

   • Single file: Move to 99_System/Archives/Projects/YYYY/ProjectName.md
   • Folder: Move to 99_System/Archives/Projects/YYYY/ProjectName/
   • Organize by year based on completion date

   For Inbox Items:

   • Move to 99_System/Archives/Inbox/YYYY/MM/filename.md
   • Organize by year and month of processing
   • Preserves chronological capture history

3. Update metadata:

   • Add archived: YYYY-MM-DD to frontmatter
   • Keep all other metadata intact

4. Preserve links:

   • Update today's daily note with archive action
   • Note: Existing wikilinks will still work from new location

5. Clean up:

   • Check for orphaned assets in 50_Resources/
   • Ask user if any should be cleaned up

Step 3: Summary Report

Present completion summary:

## Archive Complete

**Archived [N] projects to `99_System/Archives/Projects/YYYY/`:**
- [[Project1]] → Archives/Projects/2026/Project1/
- [[Project2]] → Archives/Projects/2026/Project2.md

**Archived [N] inbox items to `99_System/Archives/Inbox/YYYY/MM/`:**
- idea-note.md → Archives/Inbox/2026/01/
- quick-capture.md → Archives/Inbox/2026/01/

**Vault Status:**
- Active projects: [N]
- Inbox items: [N]
- Archived projects (total): [N]
- Archived inbox items (total): [N]

**Recommendations:**
- [ ] Review on-hold projects for potential archival
- [ ] Process remaining inbox items
- [ ] Clean up orphaned resources (if any found)

IMPORTANT RULES

• Preserve all content - Never delete, only move
• Organize by year - Use completion year for folder organization
• Update frontmatter - Add archived date
• Confirm before archiving - Let user review what will be archived
• Maintain links - Obsidian wikilinks work across locations
• Log the action - Update today's daily note

EDGE CASES

• No completed projects: Celebrate! Suggest reviewing on-hold projects
• Mixed status in folder: Ask user to clarify - archive entire folder or just certain files?
• Large projects with assets: Confirm whether to archive assets too
• Recently completed: Remind user they may want to do a project retrospective first

ARCHIVE STRUCTURE

99_System/Archives/
├── Projects/
│   ├── 2026/
│   │   ├── ProjectName/
│   │   │   ├── ProjectName.md
│   │   │   └── assets/
│   │   └── SimpleProject.md
│   └── 2025/
│       └── OldProject.md
└── Inbox/
    ├── 2026/
    │   ├── 01/
    │   │   └── processed-idea.md
    │   └── 02/
    │       └── another-note.md
    └── 2025/
        └── 12/
            └── old-capture.md

Key Distinction:

• Projects: Archived by completion year (structured work with outcomes)
• Inbox: Archived by processing year/month (quick captures and ideas)

ADDITIONAL FEATURES

Batch operations:

• Can archive multiple projects at once
• Groups by year automatically

Project retrospective (optional):

• Before archiving, offer to create a quick retrospective:
  • What went well?
  • What could be improved?
  • Key learnings
  • Add to project's Progress section

Stats tracking:

• Track number of completed projects over time
• Can generate annual summaries

EXAMPLE OUTPUT

## Items Ready for Archive

**Completed Projects (2):**
- [[Personal_OS_Setup]] - Completed on 2026-01-30
- [[NYC_Trip_Feb_2026]] - Completed on 2026-02-09

**Processed Inbox Items (1):**
- Build my personal OS with obsidian and Claude Code.md - Processed to [[Personal_OS_Setup]]

Would you like to archive these items?
(They'll be moved to 99_System/Archives/ but wikilinks will continue to work)

Options:
1. Archive all (2 projects + 1 inbox item)
2. Archive projects only
3. Archive inbox only
4. Select specific items
5. Cancel

FOLLOW-UP PROTOCOL

After archiving, suggest:

1. Weekly/monthly review to catch new completed projects
2. Set up a reminder to archive quarterly
3. Review on-hold projects - archive or reactivate?