windyboy
ee6e7518fa
Keep (8 files, all wired to .obsidian): - Templates: Daily Note Template, Project Template, book-note, quick-note - Reference: PARA_METHOD, GIT_WORKFLOW, TROUBLESHOOTING - SECURITY_ROTATION_LOG_2026-02 Delete (27 files): upstream claudesidian remnants (CHANGELOG, CONTRIBUTING, CLAUDE-BOOTSTRAP, etc.), 4 workflow docs, review reports, improvement plans, Hermes templates, duplicate/unwired templates Archive to 04_Archive/Metadata-Docs (8 files): review reports, plugin manuals, DAILY_NOTE_GUIDE, Common Claude Code Prompts
Archive
Purpose: Completed or inactive items from Projects and Areas.
What Gets Archived
- Completed projects - Move entire project folder here
- Inactive areas - Areas you're no longer maintaining
- Old resources - Outdated reference materials (use sparingly)
Archive Structure
Maintain the same folder structure:
Projects/- Completed project foldersAreas/- Inactive areasResources/- Outdated resources (if needed)
Before Archiving a Project
- Create a project summary note with:
- What was accomplished
- Key learnings
- Links to important outputs
- Update related Area notes
- Move the entire project folder here
Maintenance
- Review quarterly to see what can be deleted
- Some archived items may be reactivated
- Keep the archive organized (mirror active structure)
Tips
- Don't archive too aggressively - keep valuable reference material
- Use git history to track when things were archived
- Archived doesn't mean forgotten - you can still search and reference