AI-as-ICT Resilience (DORA x AI Act Overlap)

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-F. DORA readiness for the AI system as ICT (art-29) -> AI Act Article 15 robustness/cybersecurity conformity (ART-65) -> integrity over the combined evidence (cry-04). Maps where DORA ICT-risk duties and AI Act high-risk duties overlap for a financial AI system.

OpenChainGraph · 3 Steps cryptographic mandate Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII

Chain Stages · 3 Steps

1 ROOT · D0 node

DORA Readiness Diagnostic art-29-dora-readiness-diagnostic

DORA readiness (H1) feeds the conformity pack

MCP Call · run_dora_readiness_diagnostic

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

↓

2 D2 node

AI Act Conformity Pack Builder art-65-ai-conformity-pack-builder

robustness/cyber conformity (H2) feeds the verifier

MCP Call · build_ai_conformity_pack

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

↓

3 TERMINAL · D3 node

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

Exports composite resilience-overlap artifact with execution_hash (H3), final stage

MCP Call · verify_merkle_batch

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

Question: Supervisors asked for our DORA position on the AI platform. Where does the readiness grade sit once the twelve control answers are recorded? Run the AINumbers MCP tool `run_chain` with {"chain":"ai-governance-resilience-overlap"} and read `art-29-dora-readiness-diagnostic.grade`. Re-run with `inputs` for `art-29-dora-readiness-diagnostic`, reusing the values that result echoed, with `answers` changed so q1 through q12 are each yes. 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/ai-governance-resilience-overlap.html

AI-as-ICT Resilience (DORA x AI Act Overlap)

Ask your agent