EMIR Reconciliation & Lifecycle

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. Field reconciliation, action-type validation, and the five-dimension readiness grade each assess a separate facet of EMIR Refit reporting and are combined into one readiness attestation.

Pair two counterparties’ EMIR Refit reports by UTI and reconcile up to 148 matching fields within configurable numeric tolerance, flagging breaks (art-156) → validate action type against prior UTI state: New/Position on unreported, Modify/Correct on open, Revive on terminated (art-157) → grade the firm’s EMIR Refit reporting readiness across five dimensions: ISO 20022 cutover, UPI sourcing, UTI sharing SLA, reconciliation tolerance, and lifecycle controls; returns A–F grade (art-158). Exports readiness attestation with execution_hash. Zero network, zero PII.

OpenChainGraph · 3 Steps compliance mandate EMIR Refit 2024 148 Matching Fields W3C VC §13.11 Hash-Anchored §4 chain_depth:3 · Zero PII

Chain Stages · 3 Steps

1ROOT · D0node

EMIR Counterparty Pairing Reconciler art-156

Pairing and reconciliation feeds lifecycle event validator

MCP Call · reconcile_emir_pairing

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "reconcile_emir_pairing",
    "arguments": {
      "report_a": {
        "uti": "UTI-TEST-001",
        "notional": 1000000,
        "asset_class": "IR"
      },
      "report_b": {
        "uti": "UTI-TEST-001",
        "notional": 1000000,
        "asset_class": "IR"
      },
      "matching_fields": ["notional", "asset_class"],
      "numeric_tolerance_pct": 1
    }
  },
  "id": 1
}

↓

2MIDDLE · D1node

EMIR Lifecycle Event Validator art-157

Lifecycle validity feeds readiness diagnostic

MCP Call · validate_emir_lifecycle_event

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "validate_emir_lifecycle_event",
    "arguments": {
      "action_type": "New",
      "prior_state": "none"
    }
  },
  "id": 2
}

↓

3TERMINAL · D2node

EMIR Reporting Readiness Diagnostic art-158

Exports EMIR Refit readiness attestation with execution_hash — final stage

MCP Call · run_emir_reporting_fit

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "run_emir_reporting_fit",
    "arguments": {
      "iso20022_cutover_done": true,
      "upi_sourcing_configured": true,
      "uti_sharing_sla_met": true,
      "reconciliation_tolerance_set": true,
      "lifecycle_action_controls": true
    }
  },
  "id": 3
}

Question: Refit cutover is weeks away. Which readiness dimensions are still red before we commit the Q4 reporting calendar? Run the AINumbers MCP tool `run_chain` with {"chain":"emir-reconciliation-and-lifecycle"} and read `art-158-emir-reporting-readiness-diagnostic.grade`. 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/emir-reconciliation-and-lifecycle.html

EMIR Reconciliation & Lifecycle

Ask your agent