OpenChainGraph · DTCC Corporate Actions

Corporate Action Entitlement

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.

Two-step chain covering the DTCC Important Notice 23890-26 operator-mandated migration to ISO 20022 corporate-action messaging: message-shape validation, then deterministic dividend/rights/split entitlement math per record date. This is a DTCC operator mandate (PSE testing 2026-01, Test Facility 2026-03, PROD testing 2026-07, legacy decommission Q3 2027), a market-infrastructure migration deadline, not a regulatory deadline.

compliance_mandate
STEP 1
structure_valid and event_type feed Stage 2 corporate action entitlement recompute.
STEP 2
entitlement_computed, cash_entitlement/whole_shares: final DTC corporate-action entitlement mandate.

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.

Question: Before we book the receivable, what cash does this dividend notice pay on the held position, and does the entitlement recompute complete cleanly?
Run the AINumbers MCP tool `run_chain` with {"chain":"corporate-action-entitlement"} and read `art-547-corporate-action-entitlement-recompute.cash_entitlement`.
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/corporate-action-entitlement.html