Cohort notes: naming timers like you mean it

Our automation studio cohort surfaced a recurring issue: timer units named after scripts instead of outcomes. Reviewers could not tell whether a timer supported billing, backups, or cache warming. We updated templates to require a short outcome prefix and an owner token. The change made unit lists readable in plain systemctl output without opening files. We also added a reminder block about OnCalendar examples. People often paste crontab habits verbatim without testing daylight edge cases. The cohort ended with a peer review where half the timers intentionally failed. Learners wrote rollback notes before fixing them, which is closer to production pressure than greenfield success.