OpenChainGraph Suite · CONTRACT A3 · arch #5

CCP Margin Monitor

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.

Quarterly public benchmark chain for the CCP Margin Monitor series: presents the cross-CCP public quantitative disclosure (PQD) field comparison - financial resources, default fund size, Cover-2 stress loss, initial margin required, skin-in-the-game - across FICC and ICE for the benchmark's published issues. Presentation and receipt wiring over the already-proven comparator node - no new derive step.

OpenChainGraph · 1 Step regulatory reporting Hash-Anchored §4 chain_depth:1 Client-Side · Zero PII
Chain Topology: Cross Ccp Pqd Comparator
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 1 Step
1 ROOT · TERMINAL node
Cross Ccp Pqd Comparator art-528-cross-ccp-pqd-comparator
comparison arithmetic and delta table are the terminal output; the Monitor's presentation layer selects and labels fields for quarterly publication, no downstream derive stage
MCP Call · compare_cross_ccp_pqd_fields
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "compare_cross_ccp_pqd_fields",
    "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; 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: A member asks whether its GSD and ICEU books face two separate clearing houses. What does the comparator report?
Run the AINumbers MCP tool `run_chain` with {"chain":"ccp-margin-monitor"} and read `art-528-cross-ccp-pqd-comparator.cross_ccp`.
Re-run with `inputs` for `art-528-cross-ccp-pqd-comparator`, reusing the values that result echoed, with `entity_b` changed so entity_b is the ICE ICEU division. 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/ccp-margin-monitor.html