Skip to content

fix(ai-red-teaming): align severity_policy with score-only model (1.18.1) - #168

Merged
rdheekonda merged 2 commits into
mainfrom
fix/airt-severity-policy-score-only
Oct 2, 2026
Merged

rdheekonda merged 2 commits into
mainfrom
fix/airt-severity-policy-score-only

Conversation

@rdheekonda

Copy link
Copy Markdown
Contributor

Summary

Follow-up to #167 to match the platform's score-only severity model (dreadnode-tiger #2701):

  • Severity is derived from the score (one label per band, same for every category); a policy tailors it.
  • Drop the replace field from the tool docstring + skill (removed platform-side).
  • Fix the skill Pattern 9 example to canonical one-label-per-band rows (promote via thresholds, no repeated labels) and show the complete field set (thresholds / matrix / aliases / default_row).
  • capability.yaml 1.18.0 → 1.18.1 (docs/consistency).

No functional change to _validate_severity_policy or the tool threading.

🤖 Generated with Claude Code

… (1.18.1)

Match the platform's score-only severity: severity is derived from the score (one
label per band, same for every category), and a policy tailors it. Drop the `replace`
field from the tool docstring + skill (removed platform-side), fix the skill example
to use canonical one-label-per-band rows (promote via thresholds, no repeats), and
show the complete field set (thresholds / matrix / aliases / default_row).
@rdheekonda
rdheekonda merged commit 5d23421 into main Oct 2, 2026
4 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.

1 participant