Release v0.1.12: Configurable Match Threshold with DOB/Nationality Cross-Validation

12 February 2026

What changed

• Configurable match threshold: Set your screening sensitivity from 50% to 100% via a new slider and preset buttons (Strict 92%, Balanced 82%, Loose 72%, Very Loose 60%) in Dashboard → Settings.
• DOB cross-validation: When a person's date of birth is available, mismatched DOBs reduce the match score by 15% and matching DOBs boost it by 5%. Handles partial dates and multiple formats.
• Nationality cross-validation: Nationality mismatches penalise scores by 8%, matches boost by 3%. Includes alias support for 11 country groups (e.g. "British" = "UK" = "Great Britain").
• New Settings API: GET/PUT /api/settings/screening lets you read and update threshold and cross-validation toggles programmatically.
• All screening paths updated: Manual add, re-screen, batch re-screen, and REST API all respect your configured settings.
• Audit logging: Every settings change is logged with previous and new values.

Why it matters

False positives are the biggest day-to-day pain in sanctions screening. These cross-validation checks use structured data you already have — date of birth and nationality — to automatically suppress unlikely matches and surface real ones. The configurable threshold lets you tune sensitivity to your risk appetite instead of being locked to a single setting.

Technical notes

• New user_settings database table indexed by userId.
• Cross-validation is additive to existing fuzzy matching (Jaro-Winkler/Token-Sort/Token-Set). Missing data triggers no penalty or boost.
• REST API (/api/v1/screen) supports per-request threshold override; user settings are the default.
• Default threshold: 0.82 (Balanced). DOB and nationality cross-validation enabled by default.