sjat/boma
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

docs(todo): defer kaizen-loop automation to the notify + cron stack

Browse source 
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) <noreply@anthropic.com>
This commit is contained in:
sjat 2026-06-14 20:49:26 +02:00
parent f821006e9e
commit e5867422d0
1 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/TODO.md
View file

@ -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, …)?