Demo mode — fictional cast, real cryptography

The receipt ledger

Every message an agent proposes through Mumla leaves a signed, tamper-evident receipt — including the ones a human turned down. Open any row and verify the signature in your own browser.

  1. 15:30
    10 Jun

    Marketing agent had no grant — denied before anything ran

    Scout m•••@kund.examplemarketing.product-news

    Denied — no grantnotifyemailno receipt
  2. 11:02
    10 Jun

    Send withheld by a blast-radius cap — and receipted

    Nova m•••@kund.examplebilling.statement-ready

    Withheld — rate capnotifyemailreceipt
  3. 09:21
    10 Jun

    Overdue-invoice email — rejected; nothing was sent

    Nova e•••@kund.examplebilling.payment-reminder

    Rejected — nothing sentapprovalemailno receipt
  4. 14:32
    9 Jun

    Payment reminder to a customer — approved, then sent

    Nova m•••@kund.examplebilling.payment-reminder

    Approved & sentapprovalemailreceipt
  5. 09:12
    9 Jun

    Escalation chain — first responder timed out, second confirmed

    Atlas U-•••ops.deploy-confirmation

    Answeredescalateslackreceipt
  6. 16:40
    8 Jun

    Daily reconciliation summary — governed fire-and-forget

    Nova U-•••billing.daily-summary

    Deliverednotifyslackreceipt
  7. 10:11
    8 Jun

    Agent asked finance for a refund exception — human answered

    Atlas U-•••support.refund-exception

    Answeredask userslackreceipt

Fixtures minted 11 Jun 2026 by the Mumla substrate. The people and companies are fictional; the ed25519 DSSE signatures are real. Two entries carry no receipt on purpose: a rejected approval and a policy deny never run, so there is nothing to sign.