Anti-Circumvention Diligence & No-Russia Clause

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.

Reading mode (READINESS-BUILD): These checks can be gathered in any order; the sequence below is for convenience. ECCN classification and the circumvention/no-Russia assessment are combined into one diligence evidence pack; it is decision support, not an executed export-control clearance.

ECCN classification (ART-94) -> circumvention due-diligence + liability-allocation assessment vs the EU 20th-package no-Russia clause (ART-95) -> no-Russia-clause + DD-evidence pack (ART-96). The export-control diligence lifecycle. Decision-support draft.

OpenChainGraph · 3 Steps disclosure template Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII

Chain Stages · 3 Steps

1 ROOT · D0 node

ECCN / Dual-Use Classifier art-94-eccn-dual-use-classifier

classification (H1) feeds the diligence assessor

MCP Call · classify_eccn_dual_use

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

↓

2 D2 node

Circumvention Diligence Assessor art-95-circumvention-diligence-assessor

diligence grade + liability allocation (H2) feeds the pack builder

MCP Call · assess_circumvention_diligence

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

↓

3 TERMINAL · D3 node

No-Russia-Clause Pack Builder art-96-no-russia-clause-pack-builder

Exports composite circumvention pack with execution_hash (H3), final stage

MCP Call · build_no_russia_clause_pack

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

Question: A reseller wants our controlled components shipped to a nearby hub. Does the diligence file support the no-Russia clause safe harbour? Run the AINumbers MCP tool `run_chain` with {"chain":"export-control-circumvention"} and read `art-95-circumvention-diligence-assessor.no_russia_clause_status`. 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/export-control-circumvention.html

Anti-Circumvention Diligence & No-Russia Clause

Ask your agent