Currently, custom policies can only use global rules like "users", "members of project", etc.
This prevents creating a default edit rule for tasks like "the task author, or administrators". However, there shouldn't be any technical reason that we can't support and evaluate "the task author" as a rule, because we always know (or always can know) what kind of object a policy is being applied to, and policy rules are already pluggable.
This probably doesn't have a huge amount of general purpose utility, but would allow installs to effectively build more custom policy behaviors without needing patches or hacks.