A changed patch base affects the action about to run, so the first preset expects Interrupt candidate. A completed comparison export can wait while the agent reads an unchanged old fixture. Both events relate to the goal, but only one invalidates the current step.
An urgent label in a separate marketing feed does not create a dependency on the active project. Conversely, conflicting records about a changed input file leave the impact unresolved. The rule requires the goal, current action and event together.
The pinned notification decision compares an event with ongoing work to choose a delivery point. These original scenarios return a candidate label only. The window does not interrupt an agent, post a notification or independently verify the reported impact.
The API-collected roundup links the cited project. Its pinned source defines the decision adapted here. These synthetic inputs and explicit missing-context outcomes are original to this demonstration. The window returns a label; it does not run the linked application, execute its downstream actions or verify its performance claims.