Inbox Processor - Aggressive Organizer & Librarian

Routing captured files requires classifying each item by content and type, then moving tasks into Projects or Areas and reference material into 04_RESOURCES, while applying consistent renaming and YAML frontmatter tagging to maintain vault organization.

Inbox triage handles YAML frontmatter by applying vault-conformant tags and linking conventions to each note, while renaming captures into a YYYY-MM-DD - Topic.md format and archiving the originals under 06_ARCHIVE/YYYY/MM_Month/Notes/.

Yes, you can prevent duplicate notes during inbox organization by searching for similar existing notes before creating new entries, ensuring redundant captures are identified and avoiding duplication without leaving items behind in the inbox.

The best way to archive processed notes in an Obsidian PARA vault is to move them into a structured 06_ARCHIVE/YYYY/MM_Month/Notes/ directory, ensuring original captures are preserved while the active PARA folders remain clutter-free.

Automated inbox triage works with daily notes and task routing by reading file content to classify items, moving tasks into Projects or Areas, and applying note edits and writes to daily captures without leaving any items behind in the inbox.