Revise Org note workflow

1 files changed, 10 insertions, 7 deletions

diff --git a/README.md b/README.md
index e2579ec..b03aab2 100644
--- a/README.md
+++ b/README.md
@@ -43,7 +43,9 @@ The note system lives under `~/org/` and is organized like this:
 - `resources/` for reference material.
 - `archives/` for archived notes.
 
-This is a PARA-style layout, but the agenda is intentionally narrower than the full tree. Agenda files are discovered dynamically from `projects/`, `areas/`, and `resources/` only. Daily notes and archives are excluded from the agenda scan.
+This is a PARA-style layout, but the agenda is intentionally narrower than the full tree. Agenda files are discovered dynamically from `projects/` and `areas/` only. Daily notes, archives, and resources are excluded from the agenda scan.
+
+Folder placement carries most of the structural meaning in this setup. Denote keywords are used sparingly, with `project` kept as the only built-in structural keyword because project titles are often ambiguous outside their folder.
 
 ### Completion setup
 
@@ -76,9 +78,8 @@ emacs --batch -Q --load ./init.el
 Daily notes are plain Org files in `~/org/daily/`, named by date. When a daily note is created through the config, it starts with these headings:
 
 - `Tasks`
-- `Meetings`
 - `Notes`
-- `Open loops`
+- `Open Loops`
 
 This keeps daily capture fast without routing everything through Denote.
 
@@ -86,7 +87,7 @@ This keeps daily capture fast without routing everything through Denote.
 
 The agenda is opened through `ss/open-agenda`, bound to `C-c a`. That command explicitly loads `org-agenda`, and the config refreshes `org-agenda-files` immediately before each `org-agenda` invocation so the agenda sees the current PARA files without relying on a fixed file list.
 
-This means the agenda reflects the current project, area, and resource files at runtime instead of relying on a fixed file list.
+This means the agenda reflects the current project and area files at runtime instead of relying on a fixed file list. Daily notes, archives, and resources are outside the agenda scan.
 
 ### Capture flow
 
@@ -95,9 +96,11 @@ This means the agenda reflects the current project, area, and resource files at
 - daily tasks
 - daily notes
 - daily meetings
-- Denote-backed captures for generic notes, projects, areas, people, resources, and meetings
+- Denote-backed captures for generic notes, projects, areas, people, and resources
+
+Daily task capture writes under `Tasks`. Daily note capture and daily meeting capture both write under `Notes`, and the meeting template prefixes the heading with a timestamp and the word `meeting`.
 
-Denote captures prompt for title, keywords, and subdirectory placement where appropriate, while daily captures write directly into the current day's plain Org file.
+Denote captures still prompt for title, keywords, and subdirectory placement where appropriate, but folder placement does most of the classification work. The project capture template prepopulates the `project` keyword. Area, person, and resource captures do not inject structural keywords automatically, and there is no Denote-backed meeting capture template.
 
 ### Note creation and linking
 
@@ -108,7 +111,7 @@ Denote handles long-lived notes. The main bindings are:
 - `C-c n m` to create a PARA subdirectory from the minibuffer before capturing into it.
 - `C-c n d` to open today's daily note.
 
-Keyword prompts and directory placement are part of the workflow, not an afterthought. The config is set up so structure is created first, then capture writes into it.
+Keyword prompts and directory placement are part of the workflow, not an afterthought. The config is set up so structure is created first, then capture writes into it, with folder placement carrying most of the durable type information.
 
 ### Automatic note commits