Arc Multi-Currency Corridor Jurisdiction & Settlement

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.

Route a multi-currency Arc corridor to its per-currency home regimes and validate cross-currency settlement and Travel Rule — compliance layer, no FX economics. Per-currency jurisdiction/regime router across the partner-stablecoin set (art-111) → multi-currency PvP atomicity (511) → cross-border Travel-Rule batch validation (art-104). FX pricing is handled separately by the Arc StableFX economics chain.

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

Chain Stages · 3 Steps

1 ROOT · D0 node

Arc Multi-Currency Corridor Jurisdiction Router art-111-arc-corridor-jurisdiction-router

per-leg home regimes and disclosure gaps feed Stage 2 PvP validation

MCP Call · route_partner_stablecoin_jurisdiction

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

↓

2 D2 node

Multi-Currency PvP Validator 511-multi-currency-pvp-validator

multi-leg PvP atomicity verdict feeds Stage 3 Travel-Rule batch

MCP Call · validate_pvp_settlement

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

↓

3 TERMINAL · D3 node

TFR Travel-Rule Batch Validator art-104-tfr-travel-rule-batch-validator

Exports composite multi-currency corridor artifact with execution_hash — final stage

MCP Call · validate_tfr_travel_rule_batch

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

Question: Two stablecoin legs make up the corridor, each under its own regime. Which required disclosures is a leg still missing before the routing verdict? Run the AINumbers MCP tool `run_chain` with {"chain":"arc-multicurrency-corridor"} and read `art-111-arc-corridor-jurisdiction-router.disclosure_gaps`. Re-run with `inputs` for `art-111-arc-corridor-jurisdiction-router`, reusing the values that result echoed, with `corridor_legs` changed so the EURC leg drops its AML program disclosure. 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/arc-multicurrency-corridor.html

Arc Multi-Currency Corridor Jurisdiction & Settlement

Ask your agent