summaryrefslogtreecommitdiff
path: root/README.org
diff options
context:
space:
mode:
authorSzymon Szukalski <szymon@szymonszukalski.com>2026-04-13 10:12:26 +1000
committerSzymon Szukalski <szymon@szymonszukalski.com>2026-04-13 10:12:26 +1000
commit281ca77b74eefa81578d9195ef78cd46a832d8c9 (patch)
tree81749e1d141401a69fc4dee558c44c13285da641 /README.org
parentfea9aacb598d488a79a508906b72cdf7f3b6fe87 (diff)
Reintroduce CRM workflow in init.el
Diffstat (limited to 'README.org')
-rw-r--r--README.org40
1 files changed, 36 insertions, 4 deletions
diff --git a/README.org b/README.org
index 8c28993..33ef58c 100644
--- a/README.org
+++ b/README.org
@@ -32,6 +32,7 @@ The steady-state GC threshold is restored in =init.el=.
- package bootstrap
- UI defaults
- completion
+- CRM
- Org configuration
- capture templates
@@ -87,8 +88,8 @@ The minibuffer completion setup is simple and modern:
** Org Workflow
-The Org setup assumes a personal notes layout rooted at =~/org=, with the main workflow file at =~/org/obtf.org=.
-At startup, the configuration validates those two required paths once and shows a soft warning if either is missing.
+The Org setup assumes a personal notes layout rooted at =~/org=, with the main workflow file at =~/org/optus.org= and the CRM file at =~/org/crm.org=.
+At startup, the configuration validates those required paths once and shows a soft warning if any are missing.
Emacs still starts normally, but Org workflow features may not work as expected until the layout is in place.
The workflow itself is organized around headings in that single notes file.
@@ -104,9 +105,40 @@ Key behaviors include:
- internal heading links instead of ID-based links
- heading-respecting insertion and movement behavior
+** CRM Workflow
+
+The CRM lives in =~/org/crm.org= as a flat list of level-1 person cards.
+The implementation stays in =init.el= and restores the previous practical workflow without reintroducing the old multi-file layout.
+
+Restored capabilities include:
+
+- opening the CRM in overview mode
+- finding and narrowing to an existing card
+- adding a new card with field-aware prompts
+- alias-aware minibuffer completion that inserts canonical names
+- Marginalia annotations in person selection prompts
+- CRM completion-at-point in text and Org writing buffers
+- CRM-backed abbrevs in writing buffers, refreshed when the CRM changes
+- grouped CRM reports by role, team, manager, relationship, engagement, supplier, and location
+
+The CRM card property model is:
+
+- =ABBREV=
+- =ALIASES=
+- =ROLE=
+- =TEAM=
+- =MANAGER=
+- =RELATIONSHIP=
+- =ENGAGEMENT=
+- =SUPPLIER=
+- =LOCATION=
+- =CURRENT_FOCUS=
+
+New cards always use that property set in the drawer.
+
** Capture Templates
-The capture system stays low-friction and writes into named headings in the default notes file at =~/org/obtf.org=.
+The capture system stays low-friction and writes into named headings in the default notes file at =~/org/optus.org=.
Available templates:
@@ -146,4 +178,4 @@ Custom-generated state loaded at the end of =init.el= so Customize values overri
** =Workflow.org=
-Human-facing documentation for the workflows and keybindings enabled by this configuration.
+Human-facing documentation for the workflows, CRM commands, and keybindings enabled by this configuration.