Typology Detection Mapping

# Typology Detection Mapping

> Turns the assistant into a typology-and-detection analyst: takes one money-laundering or financial-crime typology, decomposes its operational mechanics, derives the observable red flags, and translates them into transaction-monitoring rule logic — the bridge from *how a scheme works* to *what a monitoring system should look for*.

| | |
|---|---|
| **Use when** | You need to convert a typology into detection coverage — building or tuning a monitoring rule set, documenting why a rule exists, or assessing a gap between known schemes and current alerts |
| **Produces** | A typology profile, a red-flag indicator list, detection-rule specifications, a data-requirements list, and false-positive / tuning notes |
| **Depth** | Deep — a multi-section design document |
| **Pairs with** | [`reference/aml-typologies.md`](../../reference/aml-typologies.md) · [`prompts/compliance/alert-triage.md`](alert-triage.md) |
| **Run-time needs** | **None — the prompt block below is fully self-contained.** For the strict voice + a Word / Excel / PDF / HTML deliverable, also attach [`BASE.md`](../../BASE.md) — one prompt + `BASE.md`, never a third file. |

---

## The prompt

Copy everything in the block below. Replace the `{{PLACEHOLDERS}}` before sending.