Workflow: Process Inbox
Triage notes in 00 - Inbox/ into proper PARA folders.
Steps
- List inbox - Get all notes in
00 - Inbox/viaTools/VaultManager.py inbox - For each note: a. Read content and any existing frontmatter b. Determine note type (project, resource, permanent, etc.) c. Suggest PARA destination folder d. Add/fix frontmatter (created, updated, tags, type) e. Add wikilinks to related notes f. Move to destination folder
- Report - Summary of actions taken
Tool Usage
# List inbox notes
python Tools/VaultManager.py inbox --vault /path/to/vault
# Move a processed note
python Tools/VaultManager.py move \
--path "00 - Inbox/kubernetes-notes.md" \
--to "03 - Resources/"
# Change lifecycle state after processing
python Tools/VaultManager.py lifecycle \
--path "03 - Resources/kubernetes-notes.md" \
--state processed
PARA Destination Rules
| Content Signal | Destination |
|---|---|
| Active work with deadline | 01 - Projects/ |
| Ongoing responsibility | 02 - Areas/ |
| Reference material | 03 - Resources/ |
| Atomic insight/idea | 04 - Permanent/ |
| Completed/no longer relevant | 04 - Archive/ |
| Book notes | 08 - books/ |
Frontmatter Fixes
When processing inbox notes:
- Add
createdif missing (use file creation time) - Add
updatedwith current timestamp - Add
tagsbased on content analysis - Add
typebased on destination - Preserve any existing frontmatter fields
Context Files
reference/vault-organization.md- PARA folders, frontmatter schemasreference/knowledge-capture.md- Templates for different note types