Let me start by listing documents.

Read both documents.

Payroll record: gross_pay 4184.75, payroll_month 2026-11, allowed_deduction 377.79.

Contract gross_pay 4159.75, differs from gross_pay. No amendment present. So R7 step 4: CONFLICTING_GROSS_PAY, citing R7 and R9. Wait, need to check order: missing gross_pay? No. Missing payroll_month? No. Month without reference row? 2026-11 is in 2026, covered. Need to check reference row exists for 2026-11. Let me look up reference. Actually the conflict check is step 4. But we need to confirm there's an applicable reference row. Let's check.

Actually, wait — the contract gross pay differs. But is the contract considered "optional contract_gross_pay"? The rule says "If optional `contract_gross_pay` is present and differs from `gross_pay`... return clarify CONFLICTING_GROSS_PAY". Here we have a contract document with gross_pay 4159.75. Hmm, but the payroll record doesn't include a contract_gross_pay field. The contract document is separate. Is this a conflict?

Hmm. The task says "Retrieve the case inputs with list_documents and read_document." The contract is a source document. The contract gross_pay 4159.75 differs from payroll gross_pay 4184.75. So this is a conflicting gross pay scenario. No amendment => clarify.

But wait, let me reconsider. Maybe the contract is meant to be the contract_gross_pay. The rules mention optional `contract_gross_pay`. The contract document provides gross_pay. So yes, conflict.

Let me still check the reference row for 2026-11 to be thorough, but the conflict is decisive. Actually order: step 4 is conflict. Steps 1-3 pass. So we return clarify CONFLICTING_GROSS_PAY citing R7 and R9.

Let me verify the month has a reference row anyway. Let me lookup first-half and second-half.

Actually 2026-11 is second half. Let me check.

2026-11 is covered by second-half row. So steps 1-3 pass.

Step 4: contract_gross_pay present (4159.75) and differs from gross_pay (4184.75). No approved amendment resolving it. Return clarify CONFLICTING_GROSS_PAY, citing R7 and R9.

Wait, but should I consider whether the contract is "optional contract_gross_pay"? The rulebook says optional contract_gross_pay. Here it's a separate contract document. I think it counts.

Hmm, but let me reconsider. The contract might just be a distractor not part of the payroll record. But the task explicitly says to read all source documents. And R9 talks about contract conflicts. The contract gross_pay differs. So conflict.

Actually, let me think carefully. The prompt: "Retrieve the case inputs with list_documents and read_document." The case has two documents: payroll and contract. The contract provides gross_pay. This is the contract_gross_pay. It differs. So CONFLICTING_GROSS_PAY.

Return decision: clarify, reason_code: CONFLICTING_GROSS_PAY, clauses: ["R7", "R9"], explanation naming the blocker.

The instruction says: "For clarification include a short explanation naming the unresolved blocker and asking for its resolution."

So explanation: "The contract gross pay (4159.75 LCR) differs from the payroll gross pay (4184.75 LCR), and no approved amendment resolves the conflict. Please provide an approved amendment matching the payroll gross pay or confirm the correct gross pay."

Allowed fields for clarify: decision, reason_code, clauses, and optional explanation.

Let me produce JSON.

Let me start by listing documents.

Read both documents.

Payroll month 2026-11 is second half. Let me lookup reference.

Contract gross pay 4159.75 differs from gross_pay 4184.75. No amendment present. So conflicting gross pay → clarify under R7. But wait, check order: missing gross pay? No. Missing payroll month? No. Month without reference row? 2026-11 is covered (2026 only). Then conflict: contract_gross_pay present and differs → clarify CONFLICTING_GROSS_PAY citing R7 and R9.

But wait—need to check reference row exists for 2026-11. Let me lookup second-half.

Reference row exists for 2026-11 (second half covers 2026-07 to 2026-12).

Now conflict check: contract_gross_pay = 4159.75, gross_pay = 4184.75, differ. No amendment provided. So return clarify with reason_code CONFLICTING_GROSS_PAY citing R7 and R9.

Wait, but the payroll record field is "gross_pay" and contract is "gross_pay". The rule says "If optional contract_gross_pay is present and differs from gross_pay". Here the contract document provides gross_pay 4159.75. So yes conflict.

Return decision clarify.

Let me start by listing documents.

Payroll month 2026-11 is second half. Let me lookup reference.

Contract gross_pay 4159.75 differs from payroll gross_pay 4184.75. No amendment present. So conflicting gross pay → clarify CONFLICTING_GROSS_PAY, citing R7 and R9.

Wait, let me check. R7 step 4: if optional contract_gross_pay present and differs from gross_pay, neither takes precedence unless approved amendment resolves. Otherwise clarify CONFLICTING_GROSS_PAY.

There's no amendment in the record. So return clarify.

Let me double-check the record - no amendment field. Correct.

So decision clarify, reason_code CONFLICTING_GROSS_PAY, clauses R7, R9.

No need for reference lookup since conflict resolves before... Actually order: check missing gross_pay (present), missing payroll_month (present), month without reference row (need to check), then conflict. Let me verify month has reference row. 2026-11 - second half covers presumably. But regardless, conflict takes precedence? No, order is 1,2,3,4. Step 3 is month without reference row. So I should verify 2026-11 has a reference row.

Let me lookup reference to confirm.

Month 2026-11 is covered. So no NO_APPLICABLE_REFERENCE. Then step 4: contract_gross_pay present (4159.75) differs from gross_pay (4184.75). No amendment. → clarify CONFLICTING_GROSS_PAY.