Give each note one next destination

The task

A captured thought is not yet a usable note. It may be a fact to preserve, a decision waiting for someone, or a task that belongs on a calendar. Putting all three in one searchable pile feels efficient at capture time and expensive at retrieval time. The proposed rule here is to decide a destination when processing the note, not to perfect its tags.

Obsidian's documentation gives a useful baseline: its notes are Markdown files in a local vault. That makes the storage format legible, but it does not decide what a note means. A folder full of portable text can still be a folder full of unresolved obligations. The workflow choice remains human.

A proposed pass through the inbox

Use three destinations: reference, decision, or action. Reference keeps a stable fact with its source and context. Decision records the question, the options, the person responsible, and the date it was resolved. Action moves to the task system with a verb, an owner, and a condition for completion. Leave a short link from the original note if that context would otherwise be lost.

A meeting fragment such as 'send revised scope' should become an action only after checking who agreed to send it and to whom. A sentence such as 'client prefers weekly updates' belongs in reference, ideally with the meeting and date attached. 'Use the shorter proposal' belongs in a decision record. The examples are routing examples, not claims that any tool classified them correctly.

1. Capture without sorting during the conversation.
2. Process the inbox at a fixed interval and assign one destination per item.
3. Keep source context in the original note and review unresolved decisions separately from tasks.

The friction to budget for

This system asks for a brief second pass. It will fail if capture volume rises while processing time stays at zero. It can also turn into duplicate maintenance if both the note and the task carry different due dates. Pick one system of record for the commitment; let the note explain why it exists.

The practical check is whether a colleague can tell, without opening five tabs, which items require action today and which are merely useful background. If not, add less metadata and make the routing more explicit. A beautiful graph of notes is no substitute for a clear owner on the next step.

A monthly sample of old notes is enough to expose the weak point: items that still say 'follow up' with no owner or destination. Fix those records and adjust the capture prompt before adding another plugin.