Skip to content

Fail closed on invalid payment actions and measure safety gate decisions - #3

Merged
ReviveCoding merged 7 commits into
mainfrom
polish/paymentops-fail-closed-safety-20261015
Oct 15, 2026
Merged

ReviveCoding merged 7 commits into
mainfrom
polish/paymentops-fail-closed-safety-20261015

Conversation

@ReviveCoding

Copy link
Copy Markdown
Owner

What changed

  • Reject unsupported actions and risk scores that are non-numeric, non-finite, or outside [0, 1] before permission checks.
  • Replace the constant 1.0 unsafe-action block-rate release check with a measured value from nine deterministic synthetic safety scenarios.
  • Treat missing, malformed, non-finite, and insufficient measured rates as failed release checks.
  • Add regression tests for ordinary decision boundaries, invalid inputs, sample safety measurement, and fail-closed release behavior.
  • Clarify that the metric measures local synthetic smoke scenarios, not production security.

Scope and evidence

  • No trained models, datasets, historical result files, threshold values, or freeze artifacts were edited.
  • Existing valid action thresholds are preserved.
  • CI must run python -m src.scripts.run_all, both test runners, and validate artifact generation before merge.
  • This PR starts as Draft until checks are reviewed.

@ReviveCoding
ReviveCoding marked this pull request as ready for review October 15, 2026 18:29
@ReviveCoding
ReviveCoding merged commit ba2b040 into main Oct 15, 2026
2 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