I think there might be some issue with having a manager whose constructor takes an argument. Usually you stick a reference to a manager on the model in its class declaration, in this case we'd be writing a static method on the model to instantiate a manager. This could work, but seems a little weird.

As an alternative we could make a custom manager that has a method for clobbering a set of objects, like:
``` plot = Plot.objects.filter_and_clobber(self.observer).get(pk=self.plot.pk)```

And we could have the ```filter_and_clobber``` method call ```clobber_unauthorized``` on each model in its queryset, or use a more performant, raw-sql alternative, as seen here:
https://docs.djangoproject.com/en/dev/topics/db/managers/#adding-extra-manager-methods

We might not actually have a choice, as I don't see another way to have a List/Summary/Map page with many objects that are actually clobbered. NOTE: we haven't really talked about filtering actual objects, only field, but it seems like a natural direction this might move toward.

Does that sound like it would work?