- Remove dead services: .scripts/memory/, compose.yml, initdb/, specs/ - Remove root散件: package-lock.json, install.sh, LICENSE, FIRST_RUN, .failed_images.txt, .upgrade-checklist.md, 未命名*.md, Untitled Kanban.md - Move chinese-to-english-mapping.csv → .scripts/ - Migrate 00_Inbox/Clippings/ → 04_Archive/Inbox-Clippings/ - Fix self-nesting bug: 2024/11/2023/ → 2023/ (73 files relocated) - Fix verifier false-positive on its own regex patterns
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