OpenChainGraph Suite · CONTRACT A3 · arch #5

Canton Margin Call & Collateral Mobilization Chain

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.

Margin computation (UMR/d499 for derivatives; GMRA/d349 for repo/SFT), collateral eligibility, and cash-leg finality.

OpenChainGraph · 3 Steps attestation mandate Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII
Chain Topology — Margin Call Collateral Mobilizer → Tokenized Collateral Eligibility Checker → On-Chain Cash-Leg Finality Checker
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Live Execution

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 browser
Chain Stages · 3 Steps
1 ROOT · D0 node
Margin Call Collateral Mobilizer 513-margin-call-collateral-mobilizer
branch,margin_required,collateral_gap feed Stage 2 collateral eligibility
MCP Call · mobilize_margin_collateral
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "mobilize_margin_collateral",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 D2 node
Tokenized Collateral Eligibility Checker 505-tokenized-collateral-eligibility-checker
hqla_tier,eligible_value feed Stage 3 cash-leg finality
MCP Call · check_tokenized_collateral_eligibility
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "check_tokenized_collateral_eligibility",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
3 TERMINAL · D3 node
On-Chain Cash-Leg Finality Checker 506-onchain-cash-leg-finality-checker
finality_verdict: Exports margin call collateral mandate, final stage
MCP Call · check_cash_leg_finality
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "check_cash_leg_finality",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
▶ Run this chain (live) browser · real execution · composite §4 hash
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.

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: Can we meet today's initial and variation margin call from the collateral we hold, or is there a shortfall?
Run the AINumbers MCP tool `run_chain` with {"chain":"canton-margin-call"} and read `513-margin-call-collateral-mobilizer.shortfall`.
Re-run with `inputs` for `513-margin-call-collateral-mobilizer`, reusing the values that result echoed, with `collateral_rows` changed so the one collateral row has notional 100000. 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/canton-margin-call.html