The full message, not a summary
The card shows exactly what the agent proposes to send — subject, body, recipient, purpose. What you approve is what goes out: the content is hash-bound to your decision.
Capability 02
Decisions where you already work.
No new inbox. No operator console. When an agent needs a human, the decision arrives as a card in the tools you already live in — with everything needed to decide.
Approval requested
Nova · billing agent · proposes an email to m•••@kund.example
Payment reminder — invoice #2041
Hi Maja — a friendly reminder that invoice #2041 (4 200 kr) was due on June 2. You can pay via the link in the original invoice. Reply here if anything looks wrong.
ApproveRejectsigned link
Who is asking, on the record
Every card names the agent behind the proposal — a cryptographic identity, not a shared service account. Every decision names the human — a real name on the receipt, not a hash.
Decide from anywhere
Approve or reject straight from the card — in Slack with one click, in email via a signed link that works from your phone. No login to yet another tool.
Rejections count too
A rejection is recorded with your name and your note, and nothing is sent. The ledger shows the message that did not go out — that trace is half the point.
Rich cards ship on email and Slack first; every other channel still gets a functional prompt, and the governance underneath is identical. See both outcomes in the ledger: an approved send and a rejection where nothing went out.