EMIR Inter-TR Reconciliation Cycle

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 (RUNBOOK): Run these steps in order. The ageing step works the break set the reconciliation step just built, comparing it against the prior cycle’s sealed breaks, so reconciliation has to run first.

Two-step daily cycle over the trade repository's own ISO 20022 reconciliation response and the firm's submitted state. Step 1 independently reproduces the reconciliation verdict per field against a policy-supplied field and tolerance table with a suppression list, emits agreement or disagreement with the repository, and builds a break set keyed for stable diffing across cycles. Step 2 ages that break set against the prior sealed break set, splitting newly opened, persisting and newly closed breaks and running the escalation clock. Step 1 is gated review_required for cycle sign-off, with the reporting-operations owner as reviewer. Step 2 is gated escalate once any break passes its policy ageing limit. Each break disposition is recorded as a separate annotation record naming the acting identity, so the accountability trail is per break rather than per cycle, and the prior cycle's sealed break set is referenced by subject_hash rather than mutated in place.

OpenChainGraph · 2 Steps attestation mandate Hash-Anchored §4 chain_depth:2 Client-Side · Zero PII

Chain Stages · 2 Steps

1 ROOT node review_required

EMIR Reconciliation Adjudicator art-482-emir-recon-adjudicator

Per-field agreement or disagreement with the repository plus a stably keyed break set feed the ageing and escalation-clock stage

§27 Human Accountability gate: an open break set routes cycle sign-off to review_required, with the reporting-operations owner as reviewer. Each break disposition is recorded as its own annotation record naming the acting identity, so the trail is per break rather than per cycle.

MCP Call · adjudicate_emir_reconciliation

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

↓

2 TERMINAL node escalate

EMIR Break Ageing art-483-emir-break-ageing

Ageing buckets, recurrence counts, the newly-opened / persisting / newly-closed split and escalation-clock status close the cycle bundle. Final stage.

§27 Human Accountability gate: a break past its policy ageing limit routes to escalate. The prior cycle's sealed break set is referenced by subject_hash rather than mutated in place.

MCP Call · age_emir_reconciliation_breaks

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

Question: Last night's EMIR cycle left breaks open against the TR. How old is each one, and has any aged past the escalation clock? Run the AINumbers MCP tool `run_chain` with {"chain":"emir-recon-cycle"} and read `art-483-emir-break-ageing.escalation_breached_count`. 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-recon-cycle.html

EMIR Inter-TR Reconciliation Cycle

Ask your agent