OpenChainGraph Suite · OCG v0.8.7 · Shared-Ledger Settlement · SLI-WAVE-1

Intraday Finality Attestation Receipt

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.

"Final at window Y" as deterministic, replayable evidence for a shared-ledger tokenized-deposit transfer. Settlement-asset finality-regime classification, Linea L2 finality-window classification, and an on-chain cash-leg finality check compose into a settlement-orchestrator ship-readiness attestation, then anchor as an eIDAS Art.41-aligned electronic timestamp. Built for the correspondent bank or auditor needing replayable evidence that a shared-ledger transfer is final at a stated window — not for asserting on-chain settlement this chain did not observe.

OpenChainGraph · 5 Steps attestation mandate Hash-Anchored §4 chain_depth:5 Client-Side · Zero PII
Verify-only: this receipt asserts that the supplied settlement-asset classification, L2 finality state, cash-leg finality check, and orchestrator ship-readiness attestation are internally consistent and compose into a finality verdict at the stated window. It never observes a chain or an RPC, never executes or custodies a transfer, and never asserts on-chain settlement it did not directly evaluate. Not legal advice.
ℹ The document-integrity anchor (Stage 5) is an optional terminal tail — it anchors the composite receipt digest as a timestamp but does not gate the finality verdict computed in Stages 1–4. A receipt://{execution_hash} resolver link is a planned upgrade (rides the N1 MCP Resources work) and is not yet present in the exported artifact.
Chain Topology — Asset Finality Classifier → L2 Finality Window → Cash-Leg Finality Check → Orchestrator Attestation → Document Anchor
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 5 Steps
1 ROOT node
Settlement-Asset & Legal-Finality Classifier art-59-settlement-asset-finality-classifier
finality_tier and singleness_verdict feed Stage 2 L2 finality-window classification
MCP Call · classify_settlement_asset_finality
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "classify_settlement_asset_finality",
    "arguments": {
      "settlement_asset": "commercial-bank-deposit-token",
      "finality_designation": "PFMI-compliant-FMI",
      "issuer": "regulated-bank",
      "jurisdiction": "US",
      "transfer_mechanism": "DvP-conditional",
      "singleness_test": "par-with-CBM"
    }
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 STEP node
Linea L2 Finality Window Classifier art-290-check-linea-l2-finality-window
finality_tier and safe_to_release feed Stage 3 cash-leg finality check
MCP Call · check_linea_l2_finality_window
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "check_linea_l2_finality_window",
    "arguments": {
      "asset_type": "tokenized_deposit",
      "batch_submission_status": "batched",
      "l1_finalization_status": "pending",
      "corridor_cutoff": "batched"
    }
  },
  "id": 2
}
https://mcp.ainumbers.co/mcp
↓
3 STEP node
On-Chain Cash-Leg Finality Checker 506-onchain-cash-leg-finality-checker
cash-leg verdict feeds Stage 4 settlement-orchestrator attestation
MCP Call · check_cash_leg_finality
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "check_cash_leg_finality",
    "arguments": {
      "cash_leg_type": "jpmd",
      "amount": 5000000,
      "currency": "USD",
      "finality_model": "atomic_dvp_bound",
      "reserve_attestation_available": true,
      "jurisdiction": "us"
    }
  },
  "id": 3
}
https://mcp.ainumbers.co/mcp
↓
4 STEP node
Settlement Orchestrator Attestation art-292-attest-settlement-orchestrator
composite ship-readiness grade completes the intraday finality attestation; feeds the optional document-integrity anchor
MCP Call · attest_settlement_orchestrator
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "attest_settlement_orchestrator",
    "arguments": {
      "orchestrator_manifest": {"name": "shared-ledger-settlement-orchestrator", "version": "1.0.0", "description": "Off-chain orchestrator deciding commit/halt on the shared-ledger settlement layer"},
      "decision_policy_ref": "policy/intraday-finality-v1",
      "kernel_bindings": [{"tool_id": "art-59-settlement-asset-finality-classifier"}, {"tool_id": "art-290-check-linea-l2-finality-window"}, {"tool_id": "506-onchain-cash-leg-finality-checker"}],
      "transport": "mcp-http"
    }
  },
  "id": 4
}
https://mcp.ainumbers.co/mcp
↓
5 TERMINAL · OPTIONAL node
Document Integrity & eIDAS Electronic Timestamp Anchor art-121-document-integrity-anchor
Anchors the composite receipt digest as an eIDAS Art.41-aligned electronic timestamp — final stage, optional (the finality verdict from Stages 1–4 stands without it)
MCP Call · anchor_document_integrity
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "anchor_document_integrity",
    "arguments": {
      "document_hash": "",
      "claimed_timestamp": "2026-07-14T00:00:00Z",
      "hash_algorithm": "sha256",
      "document_type": "intraday-finality-attestation-receipt"
    }
  },
  "id": 5
}
https://mcp.ainumbers.co/mcp
Export Chain Artifact
Download the §4 chain definition artifact (hash-anchored JSON) or the §13.11 W3C Verifiable Credentials view. Both derive from the chain definition — no new hash is minted. Available after hash computation.

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: Can we release the cash leg of this atomic settlement now, or does its finality model hold the payment?
Run the AINumbers MCP tool `run_chain` with {"chain":"intraday-finality-attestation"} and read `506-onchain-cash-leg-finality-checker.verdict`.
Re-run with `inputs` for `506-onchain-cash-leg-finality-checker`, reusing the values that result echoed, with `finality_model` set to "traditional_wire". 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/intraday-finality-attestation.html