List change propagation¶

When sanctions lists are updated, the engine re-screens all active customers automatically. Positive hits trigger immediate account restriction.

Module dependencies¶

Module	Title	Required?	Contract	Reason
MOD-013	Real-time sanctions screener	Required	—	Re-triggers the sanctions screener for all existing customers when a new sanctions list is published.
MOD-104	AWS shared infrastructure bootstrap	Required	—	AWS shared infrastructure provisioned by MOD-104 (EventBridge buses, S3, KMS, Kinesis, Cognito) is required before this module can be deployed.
MOD-103	Neon database platform bootstrap	Required	—	Neon database and schema provisioned by MOD-103 must exist before this module can read or write Postgres.

(No modules in this wiki currently declare a dependency on this module.)

Policy	Title	Mode	How
AML-007	Sanctions Screening Policy	`AUTO`	Existing customers screened against new designations without manual trigger — no gap between list update and re-screening
AML-006	Suspicious Activity Reporting Policy	`ALERT`	New designation matches auto-escalated to compliance — no reliance on agent to check the list

(No capabilities mapped)

Part of SD02 — Customer Identity & KYC Platform Compiled 2026-05-22 from source/entities/modules/MOD-014.yaml