The codebase is now further solidified. …

The codebase is now further solidified.  Task implementation has a very nice and easy syntax that yields a lot of power:

    // function to establish WP hooks
    function init() {
	$this->add_hook("edit_post", "post_edited");
	$this->on_completion("edit_tagline", 2);

In doing this rewrite, Tasks and Task feedback have been given more definition. I reflected those updates on my page. Even though the only display is a suggestion of what the user might do next, the complexity comes in targeting those messages correctly.

Priority is the main value, and it is a simple scalar value at that. A variety of functions assess feedback in ways that conveniently affect priority. For instance, if a user gets 3 comments pending authorization and has visited the backend 10 times, we can reflect that in a message asking them if they’d like to change their comment authorization settings:

        function init() {
	    $num_comments_pending = sizeof( get_comments(array("status"=>0)));
	    $this->add_hook_my_args($num_comments_pending, "wp_insert_comment", "comment_inserted");
	function comment_inserted($num_comments_pending, $id, $comment) {
	    if ( $num_comments_pending < 3 )
		$this->on_time( time()+2*24*60*60, $PRIORITY_DELTA );
		$this->add_hook_on_page_visits(10, "notify_change_options");

	function notify_change_options() {
	    $this->send_message( "You have unattended comments pending authorization.  Would you like to change your options?")

So tasks can either passively note priority to the TaskManager or take direct action based on given feedback. Hope to really flesh out the priority code in the next week.