Verify an overtime paycheck's garnishment withholding in four recompute stages: first compute the FLSA regular rate and overtime premium per 29 CFR 778, Subpart C, including nondiscretionary-bonus reallocation (ART-340), then compute federal income tax withholding by the IRS Publication 15-T percentage method for the declared tax year edition (ART-338), then compute gross-to-net pay with FICA at that year's Social Security wage base (ART-339), then recompute how much of the employee's disposable earnings each order in a caller-declared garnishment stack may lawfully withhold under the CCPA Title III caps, compared against a garnishment notice where one is supplied (ART-572), closing with a session receipt aggregating the run's execution hashes (CRY-05). Disposable earnings for the art-572 run are gross earnings minus legally-required deductions, using the gross and legally-required-deduction figures cited from the art-339 run; net pay is never an input to the art-572 run. The aggregate ceiling in the art-572 run, equal to the single highest individual cap present in the stack, is a documented simplification in that run's not_proven list. Wage, filing, deduction, and order figures are caller-supplied inputs; each stage is an independent recompute from its own declared inputs. A mismatch is an arithmetic finding, never a legal determination about an order's validity. Not legal advice and not tax advice.
Note: all wage, filing, deduction, and garnishment order figures are caller-supplied inputs, never inferred by the kernels. tax_year selects the Publication 15-T edition and the FICA wage base; an unsupported year fails closed rather than defaulting. A mismatch is an arithmetic finding, not a legal determination about the validity of a garnishment order.
Disposable earnings, the base for the art-572 run: disposable earnings are gross earnings minus legally-required deductions. The art-572 run declares its gross and legally-required-deduction figures from the figures cited in the art-339 run. Net pay is never an input to the art-572 run, and a run that declares net pay as its garnishment base is not this chain.
Honest limits of the art-572 run: the aggregate ceiling, equal to the single highest individual cap present in the stack, is a documented simplification listed in that run's not_proven list, not a statutory rule. A state levy uses a caller-declared percentage where one is supplied and otherwise defaults to the general CCPA cap; no 50-state table is bundled. The IRS wage-bracket exempt-amount table for a federal tax levy is out of scope. A federal tax levy is exempt from the CCPA percentage limitations and is capped in this run only at remaining disposable earnings.
Worked-example branch for bonuses: where a bonus is a percentage-of-total-earnings bonus under 29 CFR 778.210, the overtime due on the bonus is already included in the bonus itself and no retroactive regular-rate recalculation is needed for that bonus. That branch is a caller-side determination about which example applies; it is not a second computation. The art-340 run reallocates a nondiscretionary bonus amount declared for the single workweek being computed, and multi-workweek bonus proration is the caller's responsibility.
Scope: federal only. This page is not tax advice and not legal advice, and state daily and weekly overtime rules are out of scope. Use synthetic or anonymised figures in every example on this page; do not enter real employee names, real pay figures, or real account details. A mismatch against a supplied notice is an arithmetic finding, never a determination that an order is valid, enforceable, or correctly served.
compute_flsa_regular_rate{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "compute_flsa_regular_rate",
"arguments": {}
},
"id": 1
}
compute_federal_withholding{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "compute_federal_withholding",
"arguments": {}
},
"id": 1
}
compute_gross_to_net{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "compute_gross_to_net",
"arguments": {}
},
"id": 1
}
recompute_garnishment_stack{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "recompute_garnishment_stack",
"arguments": {}
},
"id": 1
}
aggregate_execution_receipts{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "aggregate_execution_receipts",
"arguments": {}
},
"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: An employee worked overtime and now faces two garnishment orders. How much can each order lawfully take from this paycheck?
Run the AINumbers MCP tool `run_chain` with {"chain":"overtime-paycheck-garnishment-check"} and read `art-572-multi-garnishment-stacking-recompute.verdict`.
Re-run with `inputs` for `art-572-multi-garnishment-stacking-recompute`, reusing the values that result echoed, with `orders` changed so with a second creditor order added to the stack. 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/overtime-paycheck-garnishment-check.html