Pre-action authority receipts for browser-agent submits

[rpelevin]

I’m testing an authority-before-action receipt pattern for browser-agent SDK workflows.

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

For this class of workflow, the boundary seems especially relevant around credentialed browser submits, account changes, exports, and external sends.

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=stagehand_browser_agent_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 this repo’s agent workflows, or would the better insertion point be somewhere else in the execution lifecycle?