OpenChainGraph Suite · CONTRACT A3

Loan Servicing Audit

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 (RUNBOOK): Read these steps in this order. The amortization schedule fixes the note's period math, the waterfall recompute checks one payment's application against the servicer's applied split, and the escrow analysis classifies the aggregate escrow position and names its remedy. Each step is supplied its own inputs; nothing is threaded between them.

Amortization schedule > loan servicing payment waterfall recompute > RESPA aggregate escrow analysis. Three independent recomputations over one loan's servicing math. Each step computes from its own declared inputs; the order is analytical, not a statutory sequence.

OpenChainGraph · 3 Steps compliance mandate Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII
Chain Topology: Amortization Schedule Builder → Loan Servicing Waterfall Recompute → RESPA Aggregate Escrow Analysis
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 3 Steps
1 ROOT node
Amortization Schedule Builder art-332-build-amortization-schedule
Builds the period-by-period amortization schedule and totals from the caller-declared note terms, with a schedule_digest over the result. Stage 1 of 3.
↓
2 D2 node
Loan Servicing Waterfall Recompute art-664-loan-servicing-waterfall-recompute
Recomputes how one payment cascades under the declared application order and diffs the per-bucket split against the servicer's applied amounts, returning a MATCHES or DIVERGES verdict with per-bucket deltas, or INDETERMINATE naming a missing field. Stage 2 of 3.
↓
3 TERMINAL · D3 node
RESPA Aggregate Escrow Analysis art-342-compute-escrow-analysis
Runs the aggregate escrow analysis over the declared balances, deposits and disbursements, classifying the account and naming the spread or refund remedy. Final stage.
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: The servicer applied this month's payment and says escrow is fine. Does an independent recompute of the split and the aggregate escrow position agree before we post the cycle?
Run the AINumbers MCP tool `run_chain` with {"chain":"servicing-audit"} and read `art-664-loan-servicing-waterfall-recompute.verdict`.
Re-run with `inputs` for `art-664-loan-servicing-waterfall-recompute`, reusing the values that result echoed, with `payment_amount` set to 9000. 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/servicing-audit.html