{
  "tool_id": "art-535-fdic370-output-file-validator",
  "kernel_id": "art-535-fdic370-output-file-validator",
  "display_name": "FDIC Part 370 Output-File Validator",
  "tool_version": "1.0.0",
  "mandate_type": "compliance_control",
  "purpose": "Validates the shape of the institution's own 12 CFR part 370 deposit-insurance-coverage output file (the section 370.10 coverage summary report structure) against its published record layout -- required field presence, malformed count/amount values, and a repeated ownership right and capacity code -- and ties the file's declared totals to a supplied art-507-determine-deposit-insurance-coverage recompute. A file-shape defect and a totals mismatch are two separate, never-merged findings: a shape problem is checked first and routes to review_required regardless of how the totals compare, and only a clean-shaped file with a totals disagreement routes to escalate. Ownership right and capacity codes stay opaque strings, exactly as in art-507; no table of part 330 ownership categories is held here. Without a supplied art-507 result there is nothing to reconcile against, so the node reports did_not_run naming that precondition rather than assuming a tie-out. Emits a section 27.4 gate-policy value plus a sibling execution_state at a predictable output_payload pointer. Not a filing and not deposit insurance advice.",
  "control_description": "Validates the shape of the institution's own 12 CFR part 370 deposit-insurance-coverage output file (the section 370.10 coverage summary report structure) against its published record layout -- required field presence, malformed count/amount values, and a repeated ownership right and capacity code -- and ties the file's declared totals to a supplied art-507-determine-deposit-insurance-coverage recompute. A file-shape defect and a totals mismatch are two separate, never-merged findings: a shape problem is checked first and routes to review_required regardless of how the totals compare, and only a clean-shaped file with a totals disagreement routes to escalate. Ownership right and capacity codes stay opaque strings, exactly as in art-507; no table of part 330 ownership categories is held here. Without a supplied art-507 result there is nothing to reconcile against, so the node reports did_not_run naming that precondition rather than assuming a tie-out. Emits a section 27.4 gate-policy value plus a sibling execution_state at a predictable output_payload pointer. Not a filing and not deposit insurance advice.",
  "declared_inputs": [],
  "declared_outputs": [],
  "kernel_digest": "sha256:10cb82f1a665d074500af23e512217234c39f79ad7f298e6f12a74eab4e2eeae",
  "trust_label": "independently verified: zkVM execution proof (risc0/groth16-bn254)",
  "data_vintage": "2026-08-04",
  "last_validated": "2026-08-04",
  "conformance_fixtures_vendored": true,
  "compute_proof_ready": "ready",
  "wave": 84,
  "source_url": "https://ainumbers.co/chaingraph/art-535-fdic370-output-file-validator.html",
  "generated_at": "2026-08-15T11:12:17.704Z"
}