OpenChainGraph Suite · CONTRACT A3 · arch #5

MLA MAPR Cashflow 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 a closed-end loan's Military Annual Percentage Rate from the borrower's actual cash flows and charges in two stages: first recompute the MAPR by the Regulation Z actuarial method over the 32 CFR 232.4(c)(1) charge set and compare it with the 36 percent cap in 232.4(b) (ART-616), then a session receipt aggregating the run's execution hashes (CRY-05). Advances, payments, timings, and charges are caller-supplied inputs; bona fide fee and application-fee exception questions are surfaced for manual review, never decided. The result is an arithmetic recompute, never a legal determination and never a covered-borrower determination. Not legal advice.

Note: all advances, payments, timings, and charges are caller-supplied inputs, never inferred by the kernel. The result is an arithmetic recompute, not a legal determination that a violation occurred and not a covered-borrower determination. Questions the regulation leaves to facts, whether a fee is bona fide and reasonable and whether the application-fee exception applies, are surfaced for manual review.

OpenChainGraph · 2 Steps compliance mandate · 32 CFR 232 Hash-Anchored §4 chain_depth:2 Client-Side · Zero PII
Chain Topology (linear): MLA MAPR Cashflow Check → Session Receipt
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 2 Steps
1 ROOT node
MLA MAPR Actuarial Recompute art-616-mla-mapr-actuarial-recompute
Recomputes a closed-end loan's Military Annual Percentage Rate from caller-supplied advances, payments, and charges by the Regulation Z actuarial method over the 32 CFR 232.4(c)(1) charge set; classifies each charge with its paragraph citation; compares the recomputed rate with the 36 percent cap in 232.4(b); surfaces bona fide fee and application-fee exception questions for manual review
MCP Call · recompute_mla_mapr_actuarial
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "recompute_mla_mapr_actuarial",
    "arguments": {}
  },
  "id": 1
}
↓
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
}
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 lender says my MAPR is 34 percent, but the fees look high. From my actual advances and payments, is it over the 36 percent cap?
Run the AINumbers MCP tool `run_chain` with {"chain":"mla-mapr-cashflow-check"} and read `art-616-mla-mapr-actuarial-recompute.exceeds_cap`.
Re-run with `inputs` for `art-616-mla-mapr-actuarial-recompute`, reusing the values that result echoed, with `payment_amount` set to 1050. 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/mla-mapr-cashflow-check.html