DORA RoI GLEIF Pre-Submission Preflight Pack

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.

Reading mode (READINESS-BUILD): These checks can be gathered in any order; the sequence below is for convenience. The RoI template set and the GLEIF/relationship checks are combined into one preparation-aid evidence pack for a named human to sign off on; it is not a submission.

DORA (EU) 2022/2554 Art. 28/30 Register of Information build, GLEIF-hardened: the RoI template set feeds a GLEIF snapshot digest and relationship-consistency check for each LEI-bearing counterparty in the register, composed into one preparation-aid evidence pack with a named-human attestation closure. Preparation aid only: not a submission, not a filing, not a determination that a submission is complete or accurate, and not a statement that any regulator has reviewed or would accept this output.

OpenChainGraph · 4 Steps compliance control Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII

Chain Stages · 4 Steps

1 ROOT node

DORA Register of Information (RoI) Builder & Cross-Validator art-466-dora-roi-builder

Constructs and cross-validates the RoI template set. The caller identifies every LEI-bearing counterparty (provider) in the resulting providers[] array to drive Stage 2/3, one GLEIF check pair per counterparty.

MCP Call · build_dora_roi_register

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

↓

2 D1 · ×N per counterparty node

GLEIF Snapshot Digest art-599-gleif-snapshot-digest

Run once per LEI-bearing counterparty from Stage 1. Produces lei/lei_checksum_valid/source_sha256/captured_at/snapshot_captured for that counterparty's gleif_snapshot slot in Stage 4.

MCP Call · digest_gleif_snapshot

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

↓

3 D2 · ×N per counterparty node

LEI Relationship Consistency Checker art-600-lei-relationship-consistency

Run once per counterparty from Stage 1, over that counterparty's pasted GLEIF Level-2 relationship record set. Produces records_assessed/consistent/violation_count for that counterparty's lei_relationship_check slot in Stage 4.

MCP Call · check_lei_relationship_consistency

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

↓

4 TERMINAL node

DORA RoI GLEIF Pre-Submission Evidence Pack art-601-dora-roi-gleif-preflight-pack

Terminal stage, page-less shard. Links the Stage 1 artifact by execution_hash + tool_id (never the raw dataset), composes each counterparty's Stage 2 + Stage 3 results, rolls up all_snapshots_captured and any_relationship_violation, and records the management-body attestation closure, producing the final preparation-aid evidence pack.

MCP Call · compute_dora_roi_gleif_preflight_pack

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

Question: Our preflight pack pins the counterparty LEI records before the DORA submission. Does every pinned LEI pass its checksum, and is the snapshot dated? Run the AINumbers MCP tool `run_chain` with {"chain":"dora-roi-gleif-preflight-pack"} and read `art-599-gleif-snapshot-digest.lei_checksum_valid`. Re-run with `inputs` for `art-599-gleif-snapshot-digest`, reusing the values that result echoed, with `lei` set to "5493001KJTIIGC8Y1R13". 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/dora-roi-gleif-preflight-pack.html

DORA RoI GLEIF Pre-Submission Preflight Pack

Ask your agent