Except it does, because it signals systemd-resolved whenever a network interface service comes up or goes down. And where do those come from? They're created automatically by systemd-init's tight coupling with the network subsystem, which it shouldn't have.

systemd-journald is a nicer example though.