Banking: Suspicious Activity Review Packet with Claude Code: Result JSON Schema
A production playbook for suspicious activity review packet in banking operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.
Audience: Financial crime teams
The problem
Financial crime teams need suspicious activity review packet to run repeatedly against transaction exports, customer profiles, alerts, case notes, and SAR criteria. In banking operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Define the outer result contract once, let the suspicious activity review packet skill own body.data, and reject terminal output that does not match the expected schema.
Tradeoffs and failure modes
Schema enforcement adds upfront design work, but removes prompt parsing from the product surface. For suspicious activity review packet, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Result shape
{
"schema_version": "argo.result.v1",
"summary": "suspicious activity review packet completed",
"body": { "type": "banking_suspicious_activity_review", "data": {}, "exceptions": [] },
"artifacts": []
}
Run this on Argo