OpenChainGraph Suite · CONTRACT A3 · arch #5

Overtime Pay 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.

Verify overtime pay for a workweek in two stages: FLSA regular-rate and overtime premium computation per 29 CFR 778 (ART-340), then a session receipt aggregating the run's execution hashes (CRY-05). Federal weekly 40-hour rule only; state daily overtime rules are out of scope. Not legal advice.

Note: art-340 rounds the regular rate to cents before computing the premium, so results can differ by one cent from payroll systems. A nondiscretionary bonus is treated as earned in the workweek entered; bonuses covering several weeks must be prorated before entry.

OpenChainGraph · 2 Steps cryptographic mandate Hash-Anchored §4 chain_depth:2 Client-Side · Zero PII
Chain Topology: TVM Annuity → Session Receipt
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 2 Steps
1 ROOT node
TVM Annuity Calculator art-340-compute-flsa-regular-rate
Produces regular_rate, overtime_hours, and overtime_premium_pay via the FLSA regular-rate method; nondiscretionary bonuses are included in the rate, discretionary bonuses excluded
MCP Call · compute_flsa_regular_rate
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "compute_flsa_regular_rate",
    "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: I earn $20/hour, worked 45 hours this week, and got a $100 performance bonus. What is my overtime pay?
Run the AINumbers MCP tool `run_chain` with {"chain":"overtime-pay-check"} and read `art-340-compute-flsa-regular-rate.overtime_premium_pay`.
Re-run with `inputs` for `art-340-compute-flsa-regular-rate`, reusing the values that result echoed, with `hours_worked_week` set to 50. 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-pay-check.html