Single-node daily FR 2052a complex-institution liquidity monitoring classification: buckets inflows/outflows by product/maturity against a caller-supplied Appendix IV-style boundary table.
This page is the chain definition (plan). To run the chain step by step in your browser, with each step's kernel executing in-page and a composite hash over the outputs, open the live runner:
▶ Run this chain in your browsercompute_fr2052a_inflow_outflow_classification{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "compute_fr2052a_inflow_outflow_classification",
"arguments": {}
},
"id": 1
}
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.
Question: Our treasury upload is in. Which maturity bucket catches the largest inflow once the classifier runs?
Run the AINumbers MCP tool `run_chain` with {"chain":"2052a-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-classify-daily.html