Approval-based execution and pre-action authority receipts

[rpelevin]

Hi maintainers/users - I am testing an authority-before-action receipt pattern for plan-first, approval-based agent execution.

The narrow question is: before an agent crosses from approved plan into consequential execution, can the runtime produce a receipt that binds the exact action, target, authority refs, policy/evidence refs, decision route, and developer-owned execution boundary?

I put a credential-free dry-run benchmark here:

https://github.com/neurarelay/relay-action-card

For this repo, the closest starting path is:

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

This is not an OpenAgentsControl approval, endorsement, integration, partnership, listing, pass, or fail claim. It is a proposed authority-before-action receipt boundary for approval-based execution.

Question for maintainers/users here: is a pre-action authority receipt useful next to approval-based execution controls, or would the better insertion point be somewhere else in the lifecycle?