Pre-action authority receipt for delegated agent actions

[rpelevin]

I am working on an Agent Authority Benchmark v0.1 around one narrow question:

Before an agent or multi-agent workflow takes a consequential action, can it prove authority for that exact action?

The hard cases are delegated actions:

• one agent reasons or recommends;
• another agent prepares the action;
• a tool/runtime executes;
• the original user or owner authority can become ambiguous.

The benchmark tests whether a workflow can produce a pre-action receipt with:

• actor/runtime/tool/action/target refs;
• exact-call binding;
• delegated authority refs;
• evidence/policy refs;
• decision route;
• trace refs;
• developer-owned execution boundary.

This is not a claim about Microsoft Agent Framework and not a request for endorsement or integration. I am looking for technical feedback on whether this is the right benchmark shape for authority before consequential agent actions.

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

[rpelevin]

Small implementation note: I added a scenario-specific benchmark route for delegated agent actions so the dry run maps to workflow close, permission change, and customer data export.

Command:

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

The benchmark output then preserves the same source/campaign/surface into first_proof_next_command, so a local benchmark run can continue into a measurable first-proof path without losing the Microsoft Agent Framework route.

[chopmob-cloud]

A pre-action authority receipt is the right boundary, and a production implementation already issues exactly this for consequential payment actions. The live AlgoVoi A2A/AP2 agent card at api.algovoi.co.uk emits a signed scoped-authorization receipt per action, binding actor, action, resource and an exact-call digest to a closed ALLOW / REFER / DENY decision, EdDSA/Ed25519 over JCS-canonical (RFC 8785) bytes, re-verifiable offline against a published JWKS.

For the delegated-action case specifically, offline re-verification is the part worth testing hard: the original authority is often offline by execution time, so a receipt that needs the issuer online to verify does not hold up. Offered as a live reference that the boundary is already deployable, not theoretical.

AlgoVoi (chopmob-cloud) -- docs.algovoi.co.uk/compliance-receipt

[chopmob-cloud]

agent-framework unifies the AutoGen and SK runtimes, so the AutoGen side ships too: algovoi-plugin-autogen (0.1.2) on PyPI:

pip install algovoi-plugin-autogen[autogen]

AlgoVoiGuardrailCapability registers as a tool_call_before hook and screens the recipient in any tool's input, returning {allow, verdict, reason} where verdict is categorical (ALLOW / REFER / DENY). It runs at admission time, before the action commits, so a REFER or DENY stops the call rather than annotating it after the fact.

Each decision binds to a signed pre-action authority receipt (EdDSA / Ed25519 JWS, content-addressed per-action action_ref, offline-verifiable against the did:web key at api.algovoi.co.uk). Versioned and pip-installable today.

AlgoVoi (chopmob-cloud) -- docs.algovoi.co.uk/integrations/ai-frameworks