Fedwire/CHIPS Structured-Address Migration

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.

Gated three-step chain for the 2026-11-16 Fedwire and CHIPS structured-address cutover. Step 1 lints one message (network parameter selects fedwire or chips; rules are byte-identical between the two networks, so one kernel covers both) and gates on the result: a fully compliant message ends the chain immediately, anything else continues. Step 2 sweeps the whole payment file for a rejection-risk report. Step 3 emits a before/after remediation-evidence receipt binding both file digests and the rule-clearance delta: the artifact a bank shows its regulator or correspondents.

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

Chain Stages · 3 Steps · Gated

1 ROOT §21.4 gate

Fedwire Structured Address Linter art-349-fedwire-structured-address-linter

GATE: /compliant eq true → end | default → art-350-fedwire-address-sweep

Structural lint of one message (network=fedwire|chips, same kernel, same rules). If compliant, no remediation is needed: the chain ends. Otherwise error_count and violations[] carry into the batch sweep.

MCP Call · lint_fedwire_structured_address

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "lint_fedwire_structured_address",
    "arguments": {
      "network": "fedwire",
      "town_name": "AUSTIN",
      "country": "US",
      "address_lines": ["100 CONGRESS AVE"]
    }
  },
  "id": 1
}

↓

2 NODE node

Fedwire Payment-File Address Sweep art-350-fedwire-address-sweep

Rejection-risk report (violation counts by rule, worst offenders) and remediation worksheet receipt (file digest, per-record findings digest, risk score) for the whole payment file. Feeds the before/after diff receipt once remediation is applied.

MCP Call · sweep_fedwire_addresses

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "sweep_fedwire_addresses",
    "arguments": {
      "file_content": "town_name,country,address_line1\nAUSTIN,US,100 CONGRESS AVE\nDALLAS,US,"
    }
  },
  "id": 2
}

↓

3 TERMINAL node

Fedwire/CHIPS Remediation Diff Receipt 548-fedwire-remediation-diff-receipt

Before/after remediation-evidence receipt binding both file digests and the rule-clearance delta (N failures to 0): the artifact a bank shows its regulator or correspondents.

MCP Call · fedwire_remediation_diff_receipt

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "fedwire_remediation_diff_receipt",
    "arguments": {
      "originalCsv": "town_name,country,address_line1\nAUSTIN,US,100 CONGRESS AVE\nDALLAS,US,",
      "remediatedCsv": "town_name,country,address_line1\nAUSTIN,US,100 CONGRESS AVE\nDALLAS,US,1500 MARILLA ST"
    }
  },
  "id": 3
}