OpenChainGraph Suite · Bank Capital & Credit Risk

FR Y-9C Schedule HC to HC-R Capital Chain

Gated two-step chain for top-tier bank holding companies (Y-9C panel, total consolidated assets >= $3B). Step 1 maps caller-declared Schedule HC balance-sheet line items into Schedule HC totals and checks the balance-sheet identity. Step 2 consumes those totals alongside caller-supplied capital components to compute Schedule HC-R capital ratios and the supplementary leverage ratio, gated dual_control(2) before the capital-adequacy result is treated as final -- any failed capital-ratio or SLR threshold requires two distinct approver sign-offs (recorded, not yet runtime-gated pending HA-RETRO-1 wiring).

OpenChainGraph · 2 Steps regulatory reporting Hash-Anchored §4 chain_depth:2 Client-Side · Zero PII
Chain Topology: Bhc Schedule Hc Balance Sheet → Bhc Schedule Hcr Capital
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 2 Steps
1 ROOT node
Bhc Schedule Hc Balance Sheet art-435-bhc-schedule-hc-balance-sheet
Schedule HC totals (total assets, total liabilities, total equity capital) feed Schedule HC-R capital-ratio computation
MCP Call · map_bhc_schedule_hc
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "map_bhc_schedule_hc",
    "arguments": {}
  },
  "id": 1
}
2 TERMINAL node dual_control(2)
Bhc Schedule Hcr Capital art-436-bhc-schedule-hcr-capital
CET1/Tier1/Total capital ratios and SLR against caller-declared, version-pinned minimums; gated dual_control(2) on a failed capital-ratio result. Final stage.
§27 Human Accountability gate: total_capital_pass=false requires dual_control(2) -- two distinct approver identities -- before the result is treated as final (recorded now, runtime-enforced once HA-RETRO-1 wires this gate).
MCP Call · map_bhc_schedule_hcr
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "map_bhc_schedule_hcr",
    "arguments": {}
  },
  "id": 1
}
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.