Checks allocation and confirmation/affirmation events against the ESMA CSDR SDR RTS 23:00 CET trade-date rule and the machine-readable-format mandate (binding Dec 2026). Computes per-event pass/fail and batch on-time rate. Part of the settlement-discipline-alloc-affirm chain.
Dec 2026 binding — 23:00 CET trade-date cutoffMachine-readable format mandateCD (EU) 2026/1536 — OJ 14.10.2026
✅ IN FORCE 7 DEC 2026: Same-day allocation/confirmation by 23:00 CET trade-date + machine-readable formats from 7 December 2026. Basis: Commission Delegated Regulation (EU) 2026/1536 of 6 July 2026 (OJ L, 14.10.2026, CELEX 32026R1536; ex C(2026) 4640 final) and ESMA revised Art. 6(2) Guidelines (final report ESMA74-2119945926-3749, 16 Oct 2026), applying from 7 December 2026.
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Event 1
Event 2
Event 3
Event 4
Event 5
–
On-Time Rate
–
Total Events
–
Format Non-Conf.
On-Time
–
Late
–
Manual Format
–
Cutoff applied: 23:00 CET (trade-date) · Mandate: Same-day allocation/confirmation + machine-readable formats applying from 7 Dec 2026 · Basis: CD (EU) 2026/1536 (OJ L, 14.10.2026, CELEX 32026R1536; ex C(2026) 4640 final) + ESMA final report ESMA74-2119945926-3749 (16 Oct 2026). Allocation/confirmation timing rules apply from 7 DEC 2026 · T+1 go-live 11 OCT 2027.
Events breakdown
OpenChainGraph v0.4 artifact · execution_hash:
–
Ask your agent
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.
Run the AINumbers MCP tool `check_allocation_affirmation`. Task: Check allocation and confirmation/affirmation events against the ESMA CSDR SDR RTS 23:00 CET trade-date rule and the machine-readable-format mandate (binding Dec 2026).
Call it with arguments: {"policy_parameters":{}}
Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, passing the full artifact the run returned (the object containing `policy_parameters` + `output_payload` + `execution_hash`; equivalently `policy_parameters` + `output_payload` with `claimed_hash`), not the bare hash string.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-81-allocation-affirmation-conformance.html#p=v1.H4sIAAAAAAAA_wECAP3_e31Dv6ajAgAAAA