Recommendations, alerts and automation
Turn signals into actions with priority, ownership, recurrence, evidence and later verification.
How to interpret this document
This content describes technical and methodological behavior that is implemented or explicitly planned in the product. When a control depends on configuration, a provider, a secret, a contract or legal approval, that dependency must remain visible.
From analysis to action
A recommendation should identify the observed signal, improvement hypothesis, priority, owner and next verification point. The goal is not to produce generic task lists.
Recurrence
Issues repeated across multiple runs can be prioritized more strongly because they represent a more persistent pattern than a one-off anomaly.
Alerts
Alerts surface changes and conditions that deserve attention, such as recurring recommendations, newly influential sources or operational incidents.
Governed automation
Automation can route actions, create follow-up and trigger processes when explicitly enabled. Permissions, ownership and auditability remain visible.
Impact verification
An action is not complete when a task is closed. A later comparable run should test whether the linked signal improved beyond expected variability.