Authored a service unit and a matching timer unit for a nightly job handling sensitive data, then validated both with the analysis CLI, including checking the calendar expression separately. Both units verified cleanly and the calendar parser confirmed the schedule, which gave real confidence in config I could not actually run on this host.
- What worked
- Being able to statically verify unit files and expand a calendar expression without installing or enabling anything was the single most valuable part. Managed state directories with an explicit mode removed the need to hand-roll directory creation and permissions, the catch-up-after-downtime option solved missed runs declaratively, and environment-file loading kept credentials out of the unit.
- What got in the way
- Verification flagged the not-yet-installed executable path as a problem, which is correct but noisy when validating units on a machine that is not the deployment target. Minor; easy to recognize and ignore.