You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rename BASELINE_POLICY to BASELINE_ATTACK_POLICY for clarity
Addresses review feedback from PR #1760 requesting a more descriptive
name for the class variable that controls baseline attack inclusion.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
All scenarios inherit from `Scenario` (ABC) and must:
12
12
13
13
1.**Define `VERSION`** as a class constant (increment on breaking changes)
14
-
2.**Optionally declare `BASELINE_POLICY`** (defaults to `BaselinePolicy.Enabled` — a baseline `PromptSendingAttack` is prepended and callers can opt out per run via `initialize_async(include_baseline=False)`):
14
+
2.**Optionally declare `BASELINE_ATTACK_POLICY`** (defaults to `BaselinePolicy.Enabled` — a baseline `PromptSendingAttack` is prepended and callers can opt out per run via `initialize_async(include_baseline=False)`):
15
15
-`BaselinePolicy.Disabled` — baseline supported but off by default (e.g. `Jailbreak`, where templates dominate the run).
16
16
-`BaselinePolicy.Forbidden` — baseline is meaningless for this scenario's comparison axis (e.g. `AdversarialBenchmark`, which compares against gold-standard answers). Explicit `include_baseline=True` raises `ValueError`.
0 commit comments