Approving what a Blob wants to do
A Blob asks before it does anything consequential. The request arrives in the thread, says exactly what it wants to do, and waits.
Work
Every step is recorded
- It stops before anything consequential
- The card says exactly what it wants to do
- Approve, and it carries on
- Every step is recorded
What always asks
Money, sending on your behalf, publishing and deleting. Always, on every autonomy mode, including Go ahead. See creating a Blob.
The approval card
It states the action, what it affects, and shows you the actual content where there is any, such as the text of an email. Approve or decline.
While it waits
The Blob's status is Waiting for you, and that shows in the thread list too, so nothing sits waiting unnoticed.
Undo
Where the underlying app allows it, an action can be reversed after the fact. Where it does not, such as an email that has already been delivered, the approval step is the control that matters, which is why sending always asks.
Seeing everything it did
The work view records each step, including Delivered, Asked for approval and Error. It is the audit trail for a teammate that works while you are not watching.