Pre-action authority receipts for agentic workflow actions

[rpelevin]

I am testing an authority-before-action receipt pattern for agentic workflow apps.

The gap I am looking at is narrow: before an agent workflow executes a consequential action, can the app prove that this exact action was authorized before execution?

For this class of workflow, the boundary seems especially relevant around external sends, data export, workflow close, permission changes, and tool execution.

Reference benchmark:
https://github.com/neurarelay/relay-action-card#agent-authority-benchmark

Dry-run command:

npm run benchmark:agent-authority -- --dry-run --json --source=github_discussion --campaign=agent_authority_week --surface=dify_agentic_workflow_authority

The benchmark is refs-only and local/dry-run: no private payloads, no downstream execution by Neura, and no claim that this project has adopted, endorsed, integrated, or been evaluated by it.

Question for maintainers/users here: is a pre-action authority receipt a useful boundary for workflow actions, or would the better insertion point be somewhere else in the execution lifecycle?