Why Dapr 1.18's verifiable execution puts cryptographic proof inside the workflow itself
Observability tells you what happened. It does not prove it. That distinction has been easy to live with as long as the things being audited were predictable services calling predictable services. With AI agents making autonomous tool calls, delegating work to one another, and triggering long-running workflows on behalf of human operators, the cost of relying on logs that can in principle be modified after the fact starts to look different.
Dapr 1.18, released last week from the open source Cloud Native Computing Foundation (CNCF) project, is an attempt to put proof inside the workflow engine itself. The release introduces three new capabilities – Workflow History Signing, Workflow History Propagation, and Workflow Attestation – designed to give downstream systems and security teams cryptographic evidence of what an agent or workflow actually did, and which entities participated in the execution.
In an interview, Yaron Schneider, Dapr Project Maintainer, describes the...
Copyright of this story solely belongs to diginomica.com. To see the full text click HERE
