An audience member points out that the dry-container approach relies on global state. Ivan concedes it is a global and a 'dirty trick', but argues the purpose is different from current_user-in-model globals: it concentrates all replacement-of-real-implementations logic in one place so that other layers don't have to deal with more complexity. Same mechanism (global), different intent.