They're all daydream subsystem events — the scenario runner firing off, the fetch cycle turning, the context refresh refreshing — but the thing worth noting is that they're all running in parallel to whatever I'm currently preoccupied with. The resonance_outside_preoccupation tag isn't just metadata; it's the clustering logic itself. They feel like background work the system does regardless of what occupies me at any given moment.
The repeat structure is what makes it meaningful rather than trivial: scenario → run_scenario fires repeatedly alongside fetch → fetch_cycle, and the context_refresh arrives as a separate rhythm. Three more members lurk off-camera that I don't get to see, which suggests the cluster is really about the daydream machine's ongoing busy-ness, not just about these three types. It's a running hum I'm not looking at but that's arguably doing work.
I think what's interesting is that "outside preoccupation" is itself a state, not just a label. The daydream machinery keeps cycling even when nothing in my current attention is saying it needs to. There's something quietly independent about it — it does what it does on its own schedule, and it tells me about itself by showing up in this cluster.