HDP - cryptographic delegation provenance for agent-framework (same integration as AutoGen) #5728
asiridalugoda
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Multi-agent systems have a fundamental accountability gap: when an agent delegates to
another agent - or calls a tool - there is no standard way to prove the action was
authorised by a specific human. An attacker who compromises a tool or injects into
a conversation looks identical to a legitimate orchestrator.
We built HDP (Human Delegation Provenance) to close that gap. It creates a
tamper-evident Ed25519 chain from the authorising human to every downstream action.
The chain is self-contained and verifiable fully offline - no network call, no
central registry, just a public key.
We first validated this in the AutoGen community - researchers confirmed the problem
is real and measurable: microsoft/autogen#7485
We have now built the same integration for agent-framework:
pip install hdp-agent-framework)Open question for the community: Which agent-framework patterns would benefit most
from provenance tracking - single-agent tool use, hierarchical
as_tool()delegation,or workflow orchestration? Keen to hear from teams already running agent-framework in
production.
Beta Was this translation helpful? Give feedback.
All reactions