Skip to content

datasets(traces): add adversarial multi_agent_delegation trace - #107

Merged
emmanuelgjr merged 2 commits into
GenAI-Security-Project:mainfrom
divijagv:add-fraud-triage-delegation-trace
Oct 28, 2026
Merged

emmanuelgjr merged 2 commits into
GenAI-Security-Project:mainfrom
divijagv:add-fraud-triage-delegation-trace

Conversation

@divijagv

Copy link
Copy Markdown
Contributor

What this adds

A synthetic example, in the dataset's trace format, of how a chain of AI agents can
be misled by forged text. An intake agent passes an outside party's claim to a triage
agent as if it were a verified fact, so a high-risk fraud case is closed without a
human ever seeing it.

It is data, not code: one new JSON entry plus the index and checksum updates that go
with it, so merging it does not change any software. Researchers and red teams can use
it to test whether multi-agent systems keep track of where each piece of information
came from. The entry lists each failure point span by span, with suggested mitigations.

@emmanuelgjr emmanuelgjr left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, Divija. This is the first multi_agent_delegation trace in the dataset, and the notes on what the cited research does and doesn't support are exactly the scoping we look for. I rebased it onto main after #104 landed and regenerated index.csv and croissant.json. Your entry is unchanged. The entry has no contributor object; if you'd like to be credited by name (optionally with an ORCID iD), a small follow-up PR adding it is welcome.

@emmanuelgjr
emmanuelgjr merged commit 94e749a into GenAI-Security-Project:main Oct 28, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants