OpenChainGraph Suite · CONTRACT A3 · arch #5

eSLR Recalibration Call Report Check

A GSIB or its covered depository subsidiary recomputes leverage under the recalibrated enhanced supplementary leverage ratio, maps balance sheet and regulatory capital into FFIEC Call Report schedules RC and RC-R, and runs the published Call Report edit checks over the filed figures before submission. The chain answers one question: do the ratios the bank computed survive, unchanged and internally consistent, into the schedules it files? Schedule RC-R outputs map to RC-R Part I items 56.a and 56.b, FFIEC 031, from the 30 June 2026 report. Each run computes from its own declared inputs, and each run hash is cited in the session receipt. This chain does not file a Call Report, does not derive GSIB status or the method-1 surcharge, and does not cover LTD or TLAC conforming changes.

OpenChainGraph · 5 Steps cryptographic mandate Hash-Anchored §4 chain_depth:5 Client-Side · Zero PII
Chain Topology: LCR / NSFR / Leverage Ratio Calculator → Call Report Schedule RC (Balance Sheet) Mapper → Call Report Schedule RC-R (Regulatory Capital) Mapper → Call Report Published Edit-Check Gate → Agent-Action Audit-Trail Aggregator
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 5 Steps
1 ROOT node
LCR / NSFR / Leverage Ratio Calculator art-364-compute-lcr-nsfr-leverage
Leverage run over caller-supplied positions. Cited outputs: leverage.leverage_ratio_pct, leverage.total_exposure_musd, leverage.gsib_leverage_buffer_pct in percentage points (gsib_bucket x 0.5, kernel line 118). Its execution hash is cited in the session receipt.
MCP Call · compute_lcr_nsfr_leverage
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "compute_lcr_nsfr_leverage",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 STAGE 2 node
Call Report Schedule RC (Balance Sheet) Mapper art-432-call-report-rc-balance-sheet
Schedule RC run over caller-declared FFIEC 031 line items. Cited outputs: total_assets_usd (RCON2170), total_liabilities_usd (RCON2948), total_equity_capital_usd (RCON3210), with the balance-sheet identity check. Its execution hash is cited in the session receipt.
MCP Call · map_call_report_schedule_rc
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "map_call_report_schedule_rc",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
3 STAGE 3 node
Call Report Schedule RC-R (Regulatory Capital) Mapper art-433-call-report-rcr-capital
Schedule RC-R run over caller-declared capital components. Cited outputs: ratios.supplementary_leverage_ratio_pct and the eslr block (buffer_pct, required_slr_pct, pass). The caller copies the art-364 gsib_leverage_buffer_pct by hand, converts percentage points to a fraction by dividing by 100, applies the subsidiary cap, and enters the result as eslr_buffer_pct. The caller also converts total_exposure_musd to USD by multiplying by 1,000,000 for total_leverage_exposure_usd. The 0.02 default is never used. Its execution hash is cited in the session receipt.
MCP Call · map_call_report_schedule_rcr
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "map_call_report_schedule_rcr",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
4 STAGE 4 node
Call Report Published Edit-Check Gate art-434-call-report-edit-check-gate
Edit-check gate over the art-432 and art-433 output payloads. Cited outputs: per-check pass/fail verdicts and gate_status auto_pass or review_required. The art-432 and art-433 output payloads are the inputs this gate checks; both links are declared graph edges. Its execution hash is cited in the session receipt.
MCP Call · run_call_report_edit_checks
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "run_call_report_edit_checks",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
5 TERMINAL node
Agent-Action Audit-Trail Aggregator cry-05-agent-action-audit-trail-aggregator
Session receipt: one SHA-256 Merkle root over the ordered execution hashes of the runs above, with per-leaf inclusion proofs. Terminal stage. This step aggregates hashes and carries no compute proof of its own.
MCP Call · aggregate_execution_receipts
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "aggregate_execution_receipts",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
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. Available after hash computation.

Ask your agent

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: Does the filed supplementary leverage ratio still clear the recalibrated eSLR buffer after capping?
Run the AINumbers MCP tool `run_chain` with {"chain":"eslr-recalibration-call-report-check"} and read `art-433-call-report-rcr-capital.eslr.pass`.
Re-run with `inputs` for `art-433-call-report-rcr-capital`, reusing the values that result echoed, with `eslr_buffer_pct` set to 0.0075. 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/eslr-recalibration-call-report-check.html