Work
View as MarkdownApprovals
A worker asks before it acts when you tell it to, and on its own for anything hard to undo. The decision is recorded. The activity feed holds everything else.
Asking for approval
Tell the worker in plain words: ask me before sending anything to a client, get approval before you change a price, confirm with Priya first. To make the rule permanent, have it added to the worker's behaviors. A worker also asks on its own for anything with a big consequence that is hard to undo: money, a first send to a client, deleting things, terms, changing who has access.
Approve and Reject in Slack
The worker posts what it is about to do, with two buttons in the conversation's own words, usually Approve and Reject. Only the first press counts. The platform replaces the buttons with one line saying who pressed which and when, so the thread is its own record. If someone other than the person it asked presses, the worker asks that person to confirm in the thread.
The activity feed
The Activity page is an append-only log of everything that happens across your company: who did it and when. Entries can never be edited or deleted. Columns: When, Actor, Kind, Summary. Filter by area, or by who did it, where system means your workers and your API keys. Every change made with a key is here under the key's name, which is why revoking a key never erases what it did.