From e5867422d09ca22bc0b0a8dda607e2a87372f715 Mon Sep 17 00:00:00 2001 From: sjat Date: Sun, 14 Jun 2026 20:49:26 +0200 Subject: [PATCH] docs(todo): defer kaizen-loop automation to the notify + cron stack Per brainstorm: ship the on-demand command + recurrence/age nudge first; revisit a scheduled headless (report-only) run once ntfy + scheduled jobs exist. Co-Authored-By: Claude Opus 4.8 (1M context) --- docs/TODO.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/TODO.md b/docs/TODO.md index d4c4b13..9c78cdf 100644 --- a/docs/TODO.md +++ b/docs/TODO.md @@ -120,6 +120,12 @@ Recurrence-triggered plus a light periodic sweep. 2. Keep appending raw signals to `docs/FRICTION.md` (live now) until the retro consumes them. + 3. **Automation deferred (revisit when the notify + cron stack is up):** the + first build is an **on-demand** command plus a light recurrence/age **nudge** + (printed reminder when the loop is overdue). Wiring a **scheduled headless + run** — report-only: it proposes add/change/**park**/remove and notifies, but + does not auto-curate/commit — waits until the notification (ntfy) + + scheduled-job stack exists. Look into automating it then. 12. **Spin-up / build order** — what is the right order of operations when spinning up from scratch (OS, DNS, Authentik, Caddy, …)?