Calibrate spam prompt confidence - #12
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Make a small, generic calibration improvement to the shared spam-classification prompt without changing Inspamity's scoring contract.
Changes
confidenceas confidence in the selected yes/no verdict; for example,is_spam=nowith confidence 90 means strong confidence that the message is not spam and therefore maps to a large negative Rspamd score.The prompt remains concise and generic: it contains no local domains, regional brands, sender allowlists, or user-specific preferences.
Validation
.venv/bin/ruff check ..venv/bin/ruff format --check ..venv/bin/pytest— 100 passed, 1 skippedNo live provider calls were made. Model-specific behavior should be compared before production deployment because prompt changes can still cause classification regressions.