Turbo::Broadcastable and MVC separation of concerns

I’m familiarising myself with the Turbo::Broadcastable documentation, and like the clean API so far.

But there is one design decision that feels odd to me:

class Clearance < ApplicationRecord
  def broadcast_later
    broadcast_prepend_later_to examiner.identity, :clearances

In this example, the model takes the decision to prepend something in the view, influencing how data is presented. However, that kind of decision is traditionally reserved for the view itself or the controller, in pure MVC separation of concerns style.

I’m just curious about the thought process behind that design choice. Was it taken out of pragmatism, to simplify the broadcast API? Or am I overthinking this?