Skip to content

MAINT: Make technique prompt placement explicit#2236

Draft
hannahwestra25 wants to merge 2 commits into
microsoft:mainfrom
hannahwestra25:hannahwestra25-explicit-technique-seed-placement
Draft

MAINT: Make technique prompt placement explicit#2236
hannahwestra25 wants to merge 2 commits into
microsoft:mainfrom
hannahwestra25:hannahwestra25-explicit-technique-seed-placement

Conversation

@hannahwestra25

Copy link
Copy Markdown
Contributor

Summary

Replace reserved sequence values with explicit prompt-placement semantics for attack-technique seeds. System prompts now request prepend behavior, and seed merging allocates dense sequences while preserving source-relative order.

Testing

Targeted model, scenario, and setup tests; Ruff and ty.

Replace reserved prompt sequence values with explicit prepend semantics during attack seed composition. Preserve placement through serialization and behavioral identity while keeping default technique hashes stable.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 0679adad-7112-481c-b3ce-846394c49889
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 0679adad-7112-481c-b3ce-846394c49889
@romanlutz

Copy link
Copy Markdown
Contributor

I like prepend. Preserve confuses me because we could end up in a situation where we have collisions (two at the same index but with different roles). What happens then? Feels undefined and could potentially result in downstream issues.

Other than "prepend" I could see "next_available" as an option but not sure that makes a lot of sense. The position is meant to be first, isn't it?

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