@daviddavis so previously, whenever we wanted to associate a task with an object, you had to add a task_id to the object.  This is meant to provide a way to bind tasks to any object without needing to add such column.  It may seem a tad silly here since tasks have an organization_id (and likely will keep it), but that is more for keeping track of what org a task was created in.  

Some examples where we would want to switch to this, would be  

owner_auto_attach_all_systems_task_id
apply_info_task_id
deletion_task_id
manifest deletion (provider task_status_id)

This more easily allows you to bind tasks to arbitrary objects.