Member Margin Call Lifecycle to Client Porting Check

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.

Reading mode (RUNBOOK): Run these steps in order. This is a real contingency path: a funded, within-SLA margin call ends the chain, and only an unmet-SLA call routes on to the client porting check.

Attests a clearing member's margin call lifecycle against its SLA window; an unmet-SLA call (disputed, escalated, or still-open past the SLA) routes to the client porting check as a contingency path, while a funded within-SLA call ends.

OpenChainGraph · 2 Steps attestation mandate Hash-Anchored §4 chain_depth:2 Client-Side · Zero PII

Chain Stages · 2 Steps

1 ROOT node

Member Margin Call Lifecycle art-531-member-margin-call-lifecycle

suggested_gate_route of end closes the chain; escalate or hold routes to Stage 2's client porting check as a contingency path

MCP Call · attest_margin_call_lifecycle

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "attest_margin_call_lifecycle",
    "arguments": {}
  },
  "id": 1
}

↓

2 TERMINAL node

Client Porting Check art-532-client-porting-check

checks whether the member's client positions and collateral are portable to a backup clearing member given the unmet-SLA margin call; terminal check

MCP Call · check_client_porting

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "check_client_porting",
    "arguments": {}
  },
  "id": 1
}

Question: A margin call issued yesterday is already funded. Does the lifecycle attestation show it met the declared SLA? Run the AINumbers MCP tool `run_chain` with {"chain":"chain-member-margin-call-to-porting"} and read `art-531-member-margin-call-lifecycle.met_within_sla`. 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/chain-member-margin-call-to-porting.html

Member Margin Call Lifecycle to Client Porting Check

Ask your agent