From 63c4618342a96e56af5027f393d458706f9dbfa0 Mon Sep 17 00:00:00 2001 From: Szymon Szukalski Date: Thu, 9 Apr 2026 16:37:03 +1000 Subject: Add Org clarify/wait workflow logging --- README.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index fce2dd2..197cb64 100644 --- a/README.md +++ b/README.md @@ -153,8 +153,16 @@ The capture model has two distinct paths: - fast operational capture goes to `~/org/journal.org` - durable notes use Denote in the PARA directories under `~/org/` -Journal capture uses a Year -> Day outline in `journal.org` with explicit -`Tasks`, `Notes`, and `Meetings` headings beneath each day entry. +`~/org/journal.org` remains the operational capture surface. Journal capture +uses a Year -> Day outline in `journal.org` with explicit `Tasks`, `Notes`, +and `Meetings` headings beneath each day entry. + +Questions that come up during the day can be tracked as Org tasks under the +day's `Tasks` heading. The intended task workflow is `TODO`, `CLARIFY`, +`WAIT`, `DONE`, and `CANCELLED`: use `CLARIFY` for open questions or ambiguity, +and `WAIT` once the question has been asked and the answer is pending. +Completing an item prompts for a note so the answer can be recorded in the +task log, and those state logs are stored in a `LOGBOOK` drawer. The configured capture templates cover: -- cgit v1.2.3