Oy, sorry for the multiple corrections here. APM's actually a little different. The APM callbacks are for specific, one-time events for specific package versions. I'm pretty sure we wouldn't expect to invoke the "after-install" callback for acs-content-repository v5.1.0 multiple times with different arguments. The same can't be said for a hypothetical "on member state change" for user 123456.