OpenChainGraph Suite · CONTRACT A3 · arch #5

Settlement-Fail Prediction Pipeline

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.

SSI conformance check (ART-80) -> fail-probability scoring on anonymized features (ART-79) -> Merkle integrity over the scored batch (cry-04). Ranks pending trades for pre-settlement intervention; targets the ~30%-of-fails SSI root cause. No PII: features are band-level.

OpenChainGraph · 3 Steps cryptographic mandate Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII
Chain Topology — SSI Conformance Checker → Settlement-Fail Predictor → Merkle Batch Verifier
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 3 Steps
1 ROOT · D0 node
SSI Conformance Checker art-80-ssi-conformance-checker
SSI match-rate + flags (H1) feed the predictor
MCP Call · check_ssi_conformance
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "check_ssi_conformance",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 D2 node
Settlement-Fail Predictor art-79-settlement-fail-predictor
ranked fail-risk list (H2) feeds the verifier
MCP Call · predict_settlement_fail
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "predict_settlement_fail",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
3 TERMINAL · D3 node
Merkle Batch Verifier cry-04-merkle-batch-verifier
Exports composite fail-prediction artifact with Merkle-root execution_hash (H3), final stage
MCP Call · verify_merkle_batch
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "verify_merkle_batch",
    "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: The overnight desk queued a trade with a missing SSI and a breached matching deadline. Will that trade settle, and what drives the call?
Run the AINumbers MCP tool `run_chain` with {"chain":"settlement-discipline-failpredict"} and read `art-79-settlement-fail-predictor.batch_fail_rate_estimate`.
Re-run with `inputs` for `art-79-settlement-fail-predictor`, reusing the values that result echoed, with `trades` changed so one trade whose SSI is missing and whose deadline is breached. 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/settlement-discipline-failpredict.html