eBL MLETR Conformance & Corridor Enforceability

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.

W-A. MLETR functional-equivalence + cross-corridor enforceability (ART-53) -> instrument/jurisdiction classification (510) -> Merkle integrity over the authoritative copy (cry-04). The flagship Wave-12 decision chain: will this electronic bill of lading hold up at both ends?

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

Chain Stages · 3 Steps

1 ROOT · D0 node

MLETR / eBL Conformance & Enforceability Validator art-53-mletr-ebl-conformance-validator

conformance_grade and enforceability_tier (H1) feed the classifier

MCP Call · validate_mletr_record

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

↓

2 D2 node

Digital Asset Regulatory Classifier 510-digital-asset-regulatory-classifier

classification verdict (H2) feeds the integrity verifier

MCP Call · classify_digital_asset_regulatory

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

↓

3 TERMINAL · D3 node

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

Exports composite enforceability artifact with 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: We tokenise the bill of lading so title moves on a DLT rail. Which regulatory regimes pick up that asset, and where does the corridor grade stand? Run the AINumbers MCP tool `run_chain` with {"chain":"digital-trade-ebl-enforceability"} and read `510-digital-asset-regulatory-classifier.classification_results`. Re-run with `inputs` for `510-digital-asset-regulatory-classifier`, reusing the values that result echoed, with `asset_type` set to "cbdc". 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-ebl-enforceability.html

eBL MLETR Conformance & Corridor Enforceability

Ask your agent