Independently recomputes a core-system-reported interest accrual figure from the caller-declared principal, annual rate, day-count basis, and days accrued, then diffs the recomputed figure against the core's reported amount under a caller-declared variance tolerance. This chain configures the existing audit recalculation suite to its interest_accrual category only, no new kernel, no new node. The day-count/compounding convention is a contract term the caller declares for each item, never inferred or defaulted. Not core-migration and not core-replacement: this recomputes and receipts one core-reported figure against an independent arithmetic derivation.
run_audit_recalc_suite{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "run_audit_recalc_suite",
"arguments": {
"tolerance": {"abs": 0, "pct": 5},
"interest_accrual": [
{
"item_id": "I-1",
"principal": 100000,
"annual_rate_pct": 6,
"days_accrued": 90,
"day_count_basis": "actual_360",
"client_reported_interest": 1490
}
]
}
},
"id": 1
}
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 client says its accruals tie. Which recomputed items still fall outside our tolerance before we sign the workpaper?
Run the AINumbers MCP tool `run_chain` with {"chain":"interest-accrual-recompute"} and read `art-463-recalc-suite.flagged_count`.
Re-run with `inputs` for `art-463-recalc-suite`, reusing the values that result echoed, with `tolerance` changed so the absolute tolerance is 6000. 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/interest-accrual-recompute.html