Skip to content

Validate redacted score-results sink policies - #35

Open
ting-hong-shieh wants to merge 1 commit into
xai-org:mainfrom
ting-hong-shieh:agent/validate-sink-policy
Open

Validate redacted score-results sink policies#35
ting-hong-shieh wants to merge 1 commit into
xai-org:mainfrom
ting-hong-shieh:agent/validate-sink-policy

Conversation

@ting-hong-shieh

Copy link
Copy Markdown

Summary

  • document the results-sink policy pair semantics and the public 9.99 redaction sentinel
  • validate policy tables, head names, numeric finiteness, ranges, and sentinel consistency at load time
  • warn when a policy contains redacted fields and explicitly disable affected lanes
  • add focused tests for valid, malformed, and redacted policies

Why

The checked-in public policy uses 9.99 to represent redacted thresholds. The cusp lane previously evaluated tau - cusp_delta; with the public values, 9.99 - 9.99 becomes 0. That arithmetic meant the sentinel did not reliably keep the lane disabled.

This change gives the sentinel explicit runtime behavior instead of relying on out-of-range comparisons. It does not propose, infer, or expose production threshold values.

Validation

  • 42 passed, 3 skipped in bdsm/tests
  • Ruff format check passed
  • Ruff core error and import checks passed
  • git diff --check passed

Addresses #25

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