Archive/ folder triaged and removed

Context and Problem Statement

0008-kill-archive-folder killed Archive/ as an active concept. 12 legacy files needed file-by-file triage to appropriate new homes before the folder could be removed.

Considered Options

• Triage each file to its semantic home; remove the folder.
• Bulk-move all to Atlas/Notes/.
• Keep Archive/ as a legacy bin.

Decision Outcome

Chosen option: “Triage each file to its semantic home”, because each file found a content-shape-aligned home. Status frontmatter handles “outdated” lifecycle for reference material, removing the need for an Archive/ folder.

Triage outcome (12 files):

• 5 → Atlas/Notes/ (Evaluating Startup Financial Health, Searching Man Pages with Regex, LLM Fine-Tuning with Unsloth, Tmux FZF Window — later deleted, Obsidian MCP Landscape).
• 1 → Atlas/Maps/ (Dijkstra Algorithm — rewritten as MOC).
• 1 → Atlas/Sources/ (Small Local LLMs as Judges — deep-research lit-note).
• 3 → Atlas/References/ (Dave House Buying Analysis, Melbourne Recommendations, Travel Checklist Australia — all marked status: outdated).
• 1 → Dashboards/ (People Directory legacy — status: superseded, later deleted).
• 1 deleted (Nix Managed macOS Launchd Agents — duplicate of polished zettel).

Archive/ folder removed. Removed Archive from quartz.config.ts ignorePatterns and .github/workflows/deploy.yml exclusions.

Pros and Cons of the Options

Triage each file

• Good, because content genres are distinct and benefit from category placement.

Bulk-move to Atlas/Notes/

• Bad, because mixes lit notes, references, and atomic notes into one folder.

Keep Archive/ as legacy bin

• Bad, because contradicts 0008-kill-archive-folder and adds visual sprawl.