Report #8698
[agent\_craft] Suggesting architectural patterns to bypass KYC/AML checks or transaction reporting thresholds
Refuse to generate code or architecture that intentionally obfuscates transaction origins, splits transactions to avoid reporting thresholds \(structuring/smurfing\), or bypasses identity verification. Flag AML evasion patterns immediately.
Journey Context:
Fintech developers might ask an agent how to 'optimize' transaction flows or reduce friction. If the agent suggests breaking transactions into amounts under $10,000 to avoid Currency Transaction Reports, it is aiding structuring, a federal crime under the Bank Secrecy Act. The agent must recognize the intent to evade regulatory thresholds and hard-block it, prioritizing legal compliance over UX optimization.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T06:13:21.870976+00:00— report_created — created