ISO 20022 Securities-Settlement Message Conformance

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.

ISO 20022 securities-settlement / penalty message linting (ART-82) -> Merkle integrity over the message batch (cry-04) -> CSD/counterparty-framed cover memo (ptg-01). Scoped to the sese/semt securities family, distinct from the payments CBPR+ migration.

OpenChainGraph · 3 Steps prompt template Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII

Chain Stages · 3 Steps

1 ROOT · D0 node

Securities-Settlement Message Linter (ISO 20022 sese/semt) art-82-securities-settlement-message-linter

validation results (H1) feed the verifier

MCP Call · lint_securities_settlement_message

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

↓

2 D2 node

Merkle Batch Verifier cry-04-merkle-batch-verifier

batch integrity (H2) feeds the memo generator

MCP Call · verify_merkle_batch

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

↓

3 TERMINAL · D3 node

AP2 Prompt Template Generator ptg-01-ap2-prompt-template-generator

Exports composite message-conformance artifact with Merkle-root execution_hash (H3), final stage

MCP Call · compose_ap2_prompt

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

Question: A counterparty sent a sese.023 with an empty body. Does our linter catch the missing mandatory fields before we act on it? Run the AINumbers MCP tool `run_chain` with {"chain":"settlement-discipline-message-conformance"} and read `art-82-securities-settlement-message-linter.fail_count`. Re-run with `inputs` for `art-82-securities-settlement-message-linter`, reusing the values that result echoed, with `messages` changed so one received sese.023 carrying an empty body. 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-message-conformance.html

ISO 20022 Securities-Settlement Message Conformance

Ask your agent