OpenChainGraph Suite · CONTRACT A3 · arch #5

Digital Trade Corridor Fit Diagnostic

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.

Single-node D0 diagnostic grading a firm/corridor A–F across legality, document digitisation, platform connectivity, trade-rule basis (eUCP/URDTT), financing, and AML/TBML for digital trade (MLETR); routes to the right Wave-12 chain.

OpenChainGraph · 1 Step agent guardrail mandate Hash-Anchored §4 chain_depth:1 Client-Side · Zero PII
Chain Topology — Digital Trade Corridor Fit Diagnostic
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 1 Step
1 ROOT · TERMINAL · D0 node
Digital Trade Corridor Fit Diagnostic art-52-digital-trade-fit-diagnostic
dim_scores and primary_recommendation route to dtc-ebl-enforceability / dtc-digital-lc / dtc-doc-integrity / dtc-counterparty-aml / dtc-trade-finance / dtc-tbml-surveillance / dtc-audit-pack
MCP Call · run_digital_trade_fit
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "run_digital_trade_fit",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
Export Artifacts
Download the §4 chain definition artifact (hash-anchored composite 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: Our corridor is paper-heavy and the bank wants to know if an electronic bill of lading is worth piloting between these two jurisdictions. What lifts the readiness grade first?
Run the AINumbers MCP tool `run_chain` with {"chain":"digital-trade-fit"} and read `art-52-digital-trade-fit-diagnostic.dim_scores.legality.score`.
Re-run with `inputs` for `art-52-digital-trade-fit-diagnostic`, reusing the values that result echoed, with `origin_jurisdiction` set to "mletr-adopted". 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/digital-trade-fit.html