OpenChainGraph Suite · CONTRACT A3 · arch #5

FR 2052a Validate then Classify Daily

Note (dated 2026-08-04): a chain composes independent computations performed in an analytical order. No step's output is carried into the next step by the execution model; each step computes from its own declared inputs. This is true of every chain on this site, including chains whose per-step copy below reads as a data handoff.

Linear two-step chain for FR 2052a daily liquidity reporting. Step 1 runs the Appendix II-a/II-b/II-c/II-d edit-check rule set against caller-supplied rows, producing a gate_status and a named list of failing edit_ids. Step 2 buckets inflows/outflows by product/maturity against a caller-supplied Appendix IV-style boundary table. Both steps always run; the edit-check result is advisory context for the classification, not a routing gate.

OpenChainGraph · 2 Steps compliance mandate Hash-Anchored §4 chain_depth:2 Client-Side · Zero PII
Chain Topology: Regrpt Editcheck Runner → Fr2052a Inflow Outflow Classifier
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 2 Steps
1 ROOT node
Published Regulatory Report Edit-Check Runner art-484-regrpt-editcheck-runner
Computes gate_status and a named list of failing edit_ids against the FR 2052a Appendix II-a/b/c/d rule set.
MCP Call · run_regrpt_edit_checks
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "run_regrpt_edit_checks",
    "arguments": {}
  },
  "id": 1
}
2 TERMINAL node
Fr2052a Inflow Outflow Classifier art-437-fr2052a-inflow-outflow-classifier
Bucket-classified inflow/outflow export for the daily FR 2052a filing layer; a bucket override without a reason_code triggers the §27 human_accountability_record.
MCP Call · compute_fr2052a_inflow_outflow_classification
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "compute_fr2052a_inflow_outflow_classification",
    "arguments": {}
  },
  "id": 2
}
Export Artifacts
Download the §4 chain definition artifact (hash-anchored composite JSON) or the §13.11 W3C Verifiable Credentials view. Both derive from the chain definition; no new hash is minted. Available after hash computation.