How fast do you alert on a new sanctions designation?

Same-day. The infrastructure published 2026-05-09 (T3.4): a delta-detection module diffs today's processed sanctions index against yesterday's; new designations are published to an SNS topic (`stratum-sanctions-new-designations`); a fan-out Lambda subscribes and matches each new designation against the monitored-entities table. Customers monitoring a name that matches the new designation get an inline Resend email within minutes of the index refresh.

The match threshold is conservative (0.85, higher than the retail screen's 0.7) to avoid noise on partial-name matches. Each alert ships: - The customer's monitored entity name + ID - The new designation name + aliases + list (OFSI / UN / EU) - The sanction regime + designation date if published - The official source URL for verification - A timestamped detection record

The alert is also written to the alert-ledger so the existing weekly monitoring digest picks it up as a safety net for any customer who missed the inline email.

What is NOT yet shipped (queued): - Twilio SMS path: blocked on Twilio account creation + SSM key (user-action). Once those land, the fan-out Lambda gains a feature-flag for SMS-as-well-as-email; existing customers can opt in per their subscription tier. - The producer-side cron Lambda that automates index refresh + delta publication every 30 minutes after OFSI's 04:00 UTC publish. Today the producer side is wired to the existing manual ingest pipeline (process.ts) with an SNS publish step at the end; a fully cron-driven producer is a follow-up CDK addition.

Competitive note: SmartSearch + ComplyAdvantage typically ship overnight-batch alerts. The signal-speed advantage of same-day is meaningful for enterprise letting-agent + accountancy customers screening high-value matters.

Last updated 2026-05-09.