Alert case management system¶

Alerts routed to analyst queue with full customer context. Case decisions (dismiss/escalate/SAR) logged immutably with analyst ID and reasoning.

Module dependencies¶

Module	Title	Required?	Contract	Reason
MOD-016	Rule-based typology engine	Required	—	Receives alerts generated by the typology engine for analyst review and SAR decision tracking.
MOD-017	ML behavioural scoring model	Optional	—	ML behavioural scoring enriches alerts with anomaly scores, improving analyst prioritisation.
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.

Module	Title	As	Contract
MOD-019	Regulatory report submission module	Hard dependency	—
MOD-037	AUSTRAC / RBNZ AML reporting pipeline	Hard dependency	—
MOD-145	Payment hold & friction engine	Hard dependency	—
MOD-149	Scam intelligence reporting & reimbursement	Hard dependency	—

Policy	Title	Mode	How
AML-005	Transaction Monitoring Policy	`LOG`	Every alert is actioned and its disposition recorded — no alerts silently discarded
AML-006	Suspicious Activity Reporting Policy	`LOG`	SAR decision trail — from alert to submission — fully auditable
GOV-006	Internal Audit Policy	`LOG`	Compliance function performance measurable — alert volumes, aging, disposition rates reportable

(No capabilities mapped)

Part of SD03 — AML Transaction Monitoring Platform Compiled 2026-05-22 from source/entities/modules/MOD-018.yaml