Archive

Finished or shelved work. We keep history instead of deleting.

Project lifecycle

Projects in 01-projects/ follow this lifecycle: active → complete → archived.

When a project completes:

1. Promote durable deliverables — templates, frameworks, and reference docs with lasting value move to 06-reference/
2. Archive working artifacts — drafts, intermediate analysis, superseded plans move here: 07-archive/{project-slug}/
3. Update the manifest — set status: archived and archived: {date} in the project’s _project.md
4. Re-index — run qmd update && qmd embed so archived docs drop out of active search priority

What goes here

• Completed project working artifacts (drafts, intermediate analysis, superseded plans)
• Retired project folders moved from 01-projects/ after completion
• Anything that had value during active work but doesn’t need to surface in future searches
• Historical imports and records

What does NOT go here

• Reference material with lasting value → stays in 06-reference/
• Deliverables that might be reused (templates, frameworks) → stays in 01-projects/ or 06-reference/
• SOPs and processes → stays in 02-sops/

Contents

• readwise-outdated/ — 22 docs. Crypto/NFT era content, outdated tech books, and misc tweets. Archived because the topics are no longer relevant to current operations.
• readwise-thin/ — 147 docs. Readwise imports with highlights too sparse to justify a full reference doc. Preserved for potential future use but not indexed in QMD. Topics span analytics tooling, data engineering, creator economy, and misc tech commentary.
• readwise-tweets/ — 72 docs. Saved tweet threads and bookmark collections. Mostly data/analytics/creator personalities. Preserved as historical record.

Total: ~241+ archived files.