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 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
}

Question: The validity edits cleared. Which maturity bucket catches the largest inflow when the classification step runs? Run the AINumbers MCP tool `run_chain` with {"chain":"2052a-validate-classify-daily"} and read `art-437-fr2052a-inflow-outflow-classifier.form_2052a.0.net_musd`. Re-run with `inputs` for `art-437-fr2052a-inflow-outflow-classifier`, reusing the values that result echoed, with `rows` changed so row r0 instead matures in 400 days. Compare the same field. Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`. Ledger, for a human re-check: https://ledger.ainumbers.co/ PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads. Chain page: https://ainumbers.co/chaingraph/chains/2052a-validate-classify-daily.html

FR 2052a Validate then Classify Daily

Ask your agent