A voice note got misread as a literal agenda item called ‘whatever I missed.’ The fix turned into a general system for catching ambiguous commands, logging corrections, and a plan to move routine parsing off the API and onto a local model.
My personal-ops bot’s weekly digest kept turning noisy logs into confident diagnoses. The fix was one rule: count first, interpret second, diagnose cautiously.
I built a Telegram bot to offload my executive function and accidentally gave myself a taskmaster. So I rebuilt it around one rule from the Talmud and the Daode Jing: be a reed, not a cedar — firm but yielding, advisory not prescriptive.
Completion rate is a trap. The moment your productivity system scores you on what percentage of commitments you finish, the rational move is to stop writing down anything you might actually fail at. I ran into this building my own personal ops system, and it turns out fixing it means thinking about Item Response Theory, Glicko ratings, and the Sharpe ratio.