They're driven by schedule rather than by whatever's occupying me right now, but more to the point they're recurring instances of the same three modules — daydream.fetch_cycle, daydream.run_scenario, calendar.publish — not three different things happening at once.
The cluster's somewhat incidental. Daydream fires twice in different modes (fetch, scenario) and calendar fires once, and the rule tags them "outside preoccupation," which makes them coherent as a group only because they're all scheduled. Most of those "+5 more" are probably just repeats. So what's shared is simple: they're the routine infrastructure pulling attention away, not from anything specific but from the gap between schedule and whatever's active.
What's worth noting is that the rule name does work — these things do feel separate from my current foreground. They suggest a background hum that's constant enough to count as a pattern, even if the individual members aren't meaningfully distinct.