Potts Effort Tracker.
We've taken the concepts of Mechanical Turk, and Event Based Applications, and Graph Data and applied them to the problem of planning and tracking effort.
When a thing needs to be done, the overall effort can be complex. It may involve multiple actions, taken by multiple actors, an those actors might be in different groups or have different roles.
Some of those actors may be human, requiring an interface - and others may be machines, requiring an API.
Moreover, actions might need to be repeated, or skipped, or added after the initial observation that our thing needs to be done.
We create an Issue and allow it to Listen out for and Trigger Events.
When an Event occurs - those Issues that are Listening can change their own State; such as active or inactive, or who they are assigned to. An Issues that Triggers an Event can also send Webhooks to other Services. Event Handers and incoming Webhooks can Trigger the creation of new Issue or Issue Sets.
Each Events that is Listened to is Handled by an Event Handers.