diff options
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 19 |
1 files changed, 11 insertions, 8 deletions
@@ -9,7 +9,9 @@ This repository configures Emacs. It does not define, create, or validate the `~ - `config.org` is the source of truth for Emacs configuration only. - `~/org` is external to this repository and must already exist. - The configuration may open files in `~/org`, but it must not create directories, create files, or validate note structure. -- `~/org/moc.org` is a normal note. The configuration may open it, but it must not create or manage it. +- `~/org/journal.org` is the operational journal. It must already exist, and the configuration may open it but must not create or manage it. +- `~/org/moc.org` is a normal note. It must already exist, and the configuration may open it but must not create or manage it. +- `~/org/areas/people/people.org` is the people CRM file. It must already exist, and the configuration may open it but must not create or manage it. - PARA is the organising model for durable notes. Folder placement carries meaning, and workflows must respect that placement. - The system optimises for speed of capture and minimal friction. - The system must prefer explicit rules over implicit behaviour and must avoid over-structuring, manual overhead, and inconsistency. @@ -19,6 +21,7 @@ This repository configures Emacs. It does not define, create, or validate the `~ These are external note-system invariants. The configuration assumes them, but it does not manage them. - `~/org` must exist. +- `~/org/journal.org` must exist. - `~/org/moc.org` must exist. - `~/org/areas/people/people.org` must exist. @@ -56,11 +59,11 @@ The current setup uses these packages and built-in modules: The note system lives under `~/org/` and is organised like this: -- `journal.org` for the operational work journal. +- `journal.org` for the operational journal. - `daily/` for older plain daily Org files that may still exist outside the active capture workflow. - `projects/` for project notes. - `areas/` for area notes. -- `areas/people/people.org` for the structured people system. +- `areas/people/people.org` for the people CRM. - `resources/` for reference material. - `archives/` for archived notes. @@ -84,9 +87,9 @@ The minibuffer stack is intentionally small: - `marginalia` adds annotations. - `corfu` handles in-buffer completion popups for text and Org buffers. -## People System +## People CRM -The people system is a structured people system (lightweight CRM) rooted at `~/org/areas/people/people.org`. +The people workflow is a CRM rooted at `~/org/areas/people/people.org`. - Each top-level heading represents one person. - Entries are strictly structured around heading text and properties. @@ -98,7 +101,7 @@ The people system is a structured people system (lightweight CRM) rooted at `~/o - Failures must surface visibly. The system must not silently fall back to stale state. - `CURRENT_FOCUS` must stay short and phrase-like so summaries and completion annotations remain readable. -Name entry uses fixed abbrevs plus the structured people system: +Name entry uses fixed abbrevs plus the people CRM: - `abbrev` provides deterministic one-shot shortcuts for fixed name expansions. - people-specific abbrevs are generated from top-level cards in `~/org/areas/people/people.org`. @@ -192,11 +195,11 @@ Agenda file selection follows the canonical rules in the `Agenda Rules` section - journal meetings - Denote-backed captures for generic notes, projects, areas, and resources -Journal task capture writes under the current day's `Tasks` heading. Journal note capture writes under `Notes`. Journal meeting capture writes under `Meetings`, and the meeting template prefixes the heading with a timestamp and the word `meeting`. +Journal task capture writes under the current day's `Tasks` heading. Journal note capture writes under `Notes`. Journal meeting capture writes under `Meetings`, and the meeting template prefixes the heading with the capture time. 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 and resource captures do not inject structural keywords automatically, and there is no Denote-backed meeting capture template. -The structured people system is intentionally outside `org-capture`: `M-x ss/people-add` writes a compact card directly into `~/org/areas/people/people.org`, keeping the people file as a fast reference file instead of another capture sink. +The people CRM is intentionally outside `org-capture`: `M-x ss/people-add` writes a compact card directly into `~/org/areas/people/people.org`, keeping the people file as a fast reference file instead of another capture sink. ### Note creation and linking |