Allocation/Affirmation Timing & Message Conformance

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.

Allocation/confirmation timing + format conformance vs the 23:00 CET trade-date mandate (ART-81) -> ISO 20022 securities-settlement message linting (ART-82) -> Merkle integrity (cry-04). Covers the binding Dec-2026 same-day machine-readable requirement.

OpenChainGraph · 3 Steps cryptographic mandate Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII

Chain Stages · 3 Steps

1 ROOT · D0 node

Allocation/Affirmation Conformance Checker art-81-allocation-affirmation-conformance

on-time rate + flagged events (H1) feed the message linter

MCP Call · check_allocation_affirmation

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

↓

2 D2 node

Securities-Settlement Message Linter (ISO 20022 sese/semt) art-82-securities-settlement-message-linter

message validation (H2) feeds the verifier

MCP Call · lint_securities_settlement_message

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

↓

3 TERMINAL · D3 node

Merkle Batch Verifier cry-04-merkle-batch-verifier

Exports composite allocation/affirmation artifact with Merkle-root execution_hash (H3), final stage

MCP Call · verify_merkle_batch

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

Question: Cutoff is 23:00 CET from December 2026. Does an allocation confirmed at 23:40 as a PDF count as conformant? Run the AINumbers MCP tool `run_chain` with {"chain":"settlement-discipline-alloc-affirm"} and read `art-81-allocation-affirmation-conformance.on_time_rate`. Re-run with `inputs` for `art-81-allocation-affirmation-conformance`, reusing the values that result echoed, with `events` changed so one allocation event confirmed at 23:40 with format pdf. 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/settlement-discipline-alloc-affirm.html

Allocation/Affirmation Timing & Message Conformance

Ask your agent