Automations and lightweight device health
An Automation owns one persistent conversation; each wake is a separate identified run using the reviewed snapshot. Release applicability is separate from source implementation, provider configuration and target authority.
Create and edit
Canonical creation/editing requires a desktop width of at least 1,024 CSS pixels. Review exact devices, selected model/reasoning, IANA timezone, schedule, AI-credit cap and any separately authorized additional-work money budget. Ordinary choices are Every weekday/day/week/month or Just once; hourly/advanced and legacy dynamic scope use their separate editor. Do not treat selected model as initially blank. Changed targets/version need fresh review; uncertain save reads the original receipt, not automatic resubmission.
Authority and run control
Runs intersect current device/workspace authority with their snapshot and local consent. Positive additional-work budgets/adoption require Admin authority. Unattended runs cannot configure Automations/monitoring or use interactive critical email. Pause prevents future due wakes; it does not cancel an active run. Bulk pause is desktop-only and excludes nonowned/changed definitions. Continue/resume creates a new run; terminal/uncertain effects are not replayed.
Only running runs execute. AI cap and DKK device-work allowance are different. Exhaustion may produce one bounded tool-free wrap-up, not unapproved continued work. A wake buys no unit by itself; actual device operations share target/date continuity with interactive work. See access for work-session meaning.
Scheduling and alerts
Supported RFC5545 rules use IANA zones, resolve gaps and one repeated-hour occurrence. Missed wakes coalesce and overlapping active work is skipped. Alerts use deterministic thresholds, latches, cooldowns, deduplication and exact-target deferred runs.
Lightweight device health
Current Disabled/Light/Full scope is cumulative: Full combines supported OS-health and resource IDs, not faster cadence. It needs Daemon >=0.23 and advertised capability. Legacy first-slice/catalogue/resource support retains its original meaning. Default cadence remains 300/900 seconds. Exact reviewed monitoring can record expressly requested necessity/setup under applicable controller/Admin authority; this is not another person's consent. Local veto/privacy publication/target authority still apply. Disable clears native queues, transfer resets scope, Rescue is excluded. Stored latest state can remain stale; non-latest readings retain seven days, event readings/alerts thirty days. Missing/offline/ineligible evidence is not healthy zero.
Critical notifications
Sending additionally needs configured existing-mail purpose, m365_graph, a retention reference, verified-member recipient and separate consent. Source defaults do not prove activation. Provider acceptance is not mailbox delivery; accepted/uncertain messages never automatically resend. CLI and API own discoverable authorized interfaces.