OPERATOR GUIDE

Automation and scheduling

Scheduled passive collection stays bounded, auditable and dry-run only.

Validated model

  • systemd user timer
  • oneshot user service
  • bounded collection cycle
  • mandatory dry-run
  • JSONL and SQLite audit writes
  • cycle status and resource measurements
  • no system-changing action in v0.0.2

Deployment-specific units

Exact unit names, paths and schedules belong to each approved deployment and are intentionally not published from a private installation. Review supplied unit files before enabling them.

Health evidence

  • timer active and next trigger
  • last service result and exit status
  • cycle count, failure and timeout totals
  • last and maximum duration
  • audit backend count parity
  • collector status summary