OpenChainGraph Suite · CONTRACT A3 · arch #5

Overdraft / NSF Fee Recompute Check

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.

Recompute overdraft and NSF fee events in two stages: an independent replay of the posted ledger under the caller's declared posting-order policy and fee schedule, diffed by post date and fee type against caller-supplied core-charged fees with a MATCHES, DIVERGES, or INDETERMINATE verdict (ART-662), then a session receipt aggregating the run's execution hashes (CRY-05). Posting order and every fee-schedule term are caller-declared inputs; a divergence is an arithmetic finding, never a determination that a fee was charged incorrectly. Not legal advice.

Note: posting order and every fee-schedule term are caller-declared inputs, never inferred by the kernel. A DIVERGES verdict is an arithmetic finding, not a determination that a fee was charged incorrectly or is owed back. Extended-overdrawn day counting follows distinct ledger post dates, not calendar days, so ledgers with date gaps undercount.

OpenChainGraph · 2 Steps compliance mandate · Reg DD 1030 / Reg E 1005 Hash-Anchored §4 chain_depth:2 Client-Side · Zero PII
Chain Topology (linear): OD/NSF Fee Recompute → Session Receipt
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 2 Steps
1 ROOT node
Overdraft / NSF Fee Recomputation art-662-odnsf-fee-recompute
Replays the posted ledger under the declared posting-order policy and fee schedule to recompute each OD and NSF fee event; recomputed totals are diffed by post date and fee type against the caller-supplied core-charged figures, with verdict MATCHES, DIVERGES, or INDETERMINATE
MCP Call · compute_odnsf_fee_recompute
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "compute_odnsf_fee_recompute",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 TERMINAL · D2 node
Agent-Action Audit-Trail Aggregator cry-05-agent-action-audit-trail-aggregator
Produces session_receipt_root, the Merkle root over the run's execution_hashes (final stage)
MCP Call · aggregate_execution_receipts
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "aggregate_execution_receipts",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
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: My bank charged two $35 overdraft fees after a $120 card purchase and a $30 ACH debit posted the same day on $100. Does an independent recompute agree?
Run the AINumbers MCP tool `run_chain` with {"chain":"overdraft-nsf-fee-recompute-check"} and read `art-662-odnsf-fee-recompute.verdict`.
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/overdraft-nsf-fee-recompute-check.html