Banking KYC File Review with Claude Code: Result JSON Schema
A production playbook for banking KYC file review in banking operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.
Audience: Bank compliance teams reviewing customer onboarding
The problem
Bank compliance teams reviewing customer onboarding need banking KYC file review to run repeatedly against KYC forms, IDs, beneficial ownership records, sanctions notes, and risk policies. 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 banking KYC file review 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 banking KYC file review, 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": "banking KYC file review completed",
"body": { "type": "banking_kyc_review", "data": {}, "exceptions": [] },
"artifacts": []
}
Run this on Argo