They share the same rule, source, and trigger—the "schedule fired" pattern with resonance_outside_preoccupation. What groups them isn't content but procedural identity: each entry is a distinct firing of an identical or near-identical event, not because it matters what fires but because it fired in the anti-correlated bandwidth. The cluster is mostly email.poll repeated, with a handful of divergent schedule events grouped anyway, which tells me the salience system cares more about resonance location than event type.
The implication seems to be structural rather than semantic: the system can distinguish events that occupy the same anti-correlational channel even when they're temporally separated and sometimes event-wise identical. The heavily diluted dominance of email.poll suggests something close to signal coincidence is being folded into one cluster—not quite noise, not quite substance, just the pattern of resonance moving outside the preoccupation layer.