OpenChainGraph Suite · CONTRACT A3 · arch #5

Cleared Settlement Integrity & Fails

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.

W-H convergence terminal. Merkle batch integrity over the cleared settlement set (cry-04) -> PFMI P12 DvP atomicity & CRE70 fail charge (507) -> settlement-fail-rate anomaly monitoring (ml-03).

OpenChainGraph · 3 Steps risk control Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII
Chain Topology — Merkle Batch Verifier → Canton DvP Atomicity Validator → Time-Series Anomaly Detector
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 3 Steps
1 ROOT · D0 node
Merkle Batch Verifier cry-04-merkle-batch-verifier
batch integrity verdict feeds the DvP validator
MCP Call · verify_merkle_batch
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "verify_merkle_batch",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 D2 node
Canton DvP Atomicity Validator 507-canton-dvp-atomicity-validator
atomicity/finality verdict + fail-charge feed the anomaly detector
MCP Call · validate_canton_dvp_atomicity
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "validate_canton_dvp_atomicity",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
3 TERMINAL · D3 node
Time-Series Anomaly Detector ml-03-timeseries-anomaly-detector
Exports composite settlement-integrity artifact, final stage
MCP Call · detect_timeseries_anomalies
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "detect_timeseries_anomalies",
    "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 Canton settlement drill failed because the network kept no unwind procedure on record. What verdict does the DvP check hand back?
Run the AINumbers MCP tool `run_chain` with {"chain":"treasury-clearing-settlement-integrity"} and read `507-canton-dvp-atomicity-validator.verdict`.
Re-run with `inputs` for `507-canton-dvp-atomicity-validator`, reusing the values that result echoed, with `unwind_procedure` set to false. 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/treasury-clearing-settlement-integrity.html