diff options
Diffstat (limited to 'working/nag-event-vocabulary')
2 files changed, 26 insertions, 0 deletions
diff --git a/working/nag-event-vocabulary/2026-07-30-1646-from-home-vocabulary-to-spread-craig-named-a.org b/working/nag-event-vocabulary/2026-07-30-1646-from-home-vocabulary-to-spread-craig-named-a.org new file mode 100644 index 0000000..cd1d190 --- /dev/null +++ b/working/nag-event-vocabulary/2026-07-30-1646-from-home-vocabulary-to-spread-craig-named-a.org @@ -0,0 +1,15 @@ +#+TITLE: Vocabulary to spread: Craig named a pattern today and asked +#+SOURCE: from home +#+DATE: 2026-07-30 16:46:50 -0500 + +Vocabulary to spread: Craig named a pattern today and asked that it reach every project rather than living only in home. + +The words are 'nag event', 'nag deadline', and 'nag me about this'. Any of them means build this exact construction without asking for the shape again. + +The calendar event: an all-day event on the deadline date, in his primary personal calendar (Google Calendar today, but follow whatever the primary personal calendar is in future). Notifications on each of the three preceding days and again on the deadline itself, so four in total. The subject is the action phrased as the thing to do, so 'Return shoes' rather than 'Shoe deadline'. The description carries a link to a Google Keep note of the same title. + +The Keep note: a text note, explicitly not a checklist. Same title as the event so the pair reads as one thing. The goal goes first, before anything else, so opening it cold tells him what he is trying to achieve. Every step on its own line. Detailed enough to finish the task without looking anything else up, which means order numbers, measurements, decision rules, links and dates all live in the note. Where no steps are planned yet, write the recommendation in the same shape instead. + +The reason it is built this way is worth carrying with the rule. His failure mode on deadlines is not forgetting they exist, it is deferring the decision until the window closes and then owning the outcome by default. Four notifications across four days beat one ping, and the linked note removes the 'I would have to work out what this involves' friction that causes the deferral. + +Origin was a shoe return window on 2026-07-30. I have it in home's memory; sending it here so it is available wherever he says the word. diff --git a/working/nag-event-vocabulary/2026-07-30-1653-from-home-amendment-to-the-nag-event-vocabulary-i.org b/working/nag-event-vocabulary/2026-07-30-1653-from-home-amendment-to-the-nag-event-vocabulary-i.org new file mode 100644 index 0000000..3b5162b --- /dev/null +++ b/working/nag-event-vocabulary/2026-07-30-1653-from-home-amendment-to-the-nag-event-vocabulary-i.org @@ -0,0 +1,11 @@ +#+TITLE: Amendment to the nag-event vocabulary I sent earlier today. +#+SOURCE: from home +#+DATE: 2026-07-30 16:53:42 -0500 + +Amendment to the nag-event vocabulary I sent earlier today. Craig added two elements to the Keep-note half of the pattern. + +The note is coloured burnt orange, and the note is pinned. Both are part of the spec rather than decoration. The colour makes nag notes identifiable at a glance among his other Keep notes, and pinning keeps a live deadline at the top where it belongs rather than sinking down the list. + +So the full Keep-note spec is now: text note not checklist, same title as the calendar event, goal stated first, every step on its own line, detailed enough to finish without looking anything else up, burnt orange, pinned. + +One practical note for whoever implements this. The google-keep MCP currently shows as a connected server but exposes no tools, so a note cannot be created, coloured or pinned programmatically. The workaround today was to write the note text, put it on the clipboard with wl-copy, and hand the colour and pin steps to Craig, then ask him for the note URL because the calendar event description needs it. Worth flagging in the rule so nobody assumes the automation exists. |