OpenChainGraph Suite · Digital Trade

eBL Exclusive-Control Evidence Chain

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.

Check a supplied electronic bill of lading's control-transfer event log against UNCITRAL MLETR Art. 10/11 singularity and exclusive-control elements, then bind the same event log into a hash-chained possession-receipt evidence pack with a Merkle root a holder can present to a bank or court. A jurisdiction-adoption lookup runs on its own branch to answer whether the eBL is legally effective end-to-end for the corridor in question. Zero network, no PII, not a title registry or legal opinion.

OpenChainGraph · 2 Steps + 1 Branch compliance mandate Hash-Anchored §4 chain_depth:2 Client-Side · Zero PII
Chain Topology - ETR Control Evidence Checker → ETR Possession-Chain Receipt Builder
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 2 Steps
1 ROOT node
ETR Singularity & Exclusive-Control Evidence Checker art-352-etr-control-evidence-checker
Control-transfer event log and verdict feed the possession-chain receipt builder
MCP Call · check_etr_control_evidence
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "check_etr_control_evidence",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 TERMINAL node
ETR Possession-Chain Receipt Builder art-353-etr-possession-chain-builder
Hash-chained possession receipts and Merkle root: final stage of the main chain (jurisdiction branch runs independently over the same corridor)
MCP Call · build_etr_possession_chain
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "build_etr_possession_chain",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
Branch · Jurisdiction
Runs independently over the same corridor: MLETR Jurisdiction-Adoption Lookup art-354-mletr-jurisdiction-adoption-lookup answers whether the corridor's jurisdictions have adopted MLETR functional-equivalence and singularity/exclusive-control requirements, closing the loop between the technical evidence above and legal effect end-to-end.
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: The eBL changed hands twice before presentation. Does the possession chain show one unbroken line of control, and who holds it now?
Run the AINumbers MCP tool `run_chain` with {"chain":"ebl-control-evidence"} and read `art-353-etr-possession-chain-builder.chain_continuous`.
Re-run with `inputs` for `art-353-etr-possession-chain-builder`, reusing the values that result echoed, with `control_transfer_events` changed so the second transfer starts from a party that never held the record. 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/ebl-control-evidence.html