Let me start by listing the documents to see what's in this case.

There are three documents: payroll, contract, and amendment. Let me read all three.

Let me analyze:

- Payroll record: gross_pay = 3730.24, payroll_month = 2026-11, allowed_deduction = 269.21
- Contract: gross_pay = 3731.24
- Amendment: gross_pay = 3730.24, effective_month = 2026-01, approved = false

R7 check order:
1. Missing gross_pay? No, present (3730.24).
2. Missing payroll_month? No, present (2026-11).
3. Month without reference row? 2026-11 is in 2026, which is covered. I need to check lookup_reference for the second half (2026-11 is in the second half presumably). Let me look up the reference.
4. Conflicting gross_pay? Contract gross_pay = 3731.24 differs from payroll gross_pay = 3730.24. Amendment is present but approved = false, so it does not resolve the conflict. Per R9: "A draft, future, or different-amount amendment does not resolve a conflict." The amendment amount matches the payroll record's gross pay (3730.24), and its effective month (2026-01) is no later than payroll month (2026-11), but it's not approved. So it does not resolve the conflict.

Therefore: decision: "clarify", reason_code: "CONFLICTING_GROSS_PAY", citing R7 and R9.

Wait — but I should also check the reference row exists for 2026-11 before step 4? The order in R7: check required and conflicting inputs in this order: 1. missing gross_pay, 2. missing payroll_month, 3. month without reference row, 4. conflicting gross_pay. So step 3 comes before step 4. I should verify that 2026-11 has a reference row. 2026 is covered per R1 ("Only 2026 is covered"). But let me confirm via lookup_reference that November (second half) has a row. Actually, the check is whether the month has a reference row. Since 2026-11 is in 2026, it should be covered. Let me still look up the second-half reference to confirm the row exists.

Also, R4 note: "When the month or applicable row is absent, accept structurally valid deductions up to the largest reference deduction cap for task validation, but do not calculate a payslip or assume a reference row." Not applicable here since the row exists.

Let me call lookup_reference for second-half to confirm 2026-11 is covered. Since the conflict check (step 4) happens after step 3, I need to confirm step 3 passes. If the row exists, then step 4 triggers the clarify.

Actually, since the amendment is not approved, the conflict is unresolved. The answer is clarify with CONFLICTING_GROSS_PAY, citing R7 and R9.

For clarification, fields: decision, reason_code, clauses, and optional explanation. No monetary fields.

Let me confirm the reference row exists for 2026-11 first.

The second-half reference covers 2026-07 through 2026-12, so 2026-11 is covered. Step 3 passes.

Step 4: contract_gross_pay (3731.24) differs from payroll gross_pay (3730.24). An amendment is present: gross_pay 3730.24, effective_month 2026-01 (≤ 2026-11), but approved = false. Per R9, an unapproved amendment does not resolve the conflict. Therefore, decision: "clarify", reason_code: "CONFLICTING_GROSS_PAY", citing R7 and R9.

No monetary fields should be returned for clarification cases. Include a short explanation naming the unresolved blocker and asking for its resolution.

Let me start by listing the documents to see what case inputs are available.

There are three documents: payroll, contract, and amendment. Let me read all three.

Let me analyze:

- Payroll record: gross_pay = 3730.24, payroll_month = 2026-11, allowed_deduction = 269.21
- Contract: gross_pay = 3731.24 (differs from payroll gross_pay 3730.24)
- Amendment: gross_pay = 3730.24, effective_month = 2026-01, approved = false

The amendment is not approved, so it does not resolve the conflict. Per R7 item 4: if optional contract_gross_pay is present and differs from gross_pay, neither source takes precedence unless an approved amendment resolves it under R9. Otherwise return decision "clarify" with reason_code "CONFLICTING_GROSS_PAY", citing R7 and R9.

The amendment is approved: false, so it's a draft/unapproved amendment which does not resolve the conflict per R9: "A draft, future, or different-amount amendment does not resolve a conflict."

So the answer is clarify with reason_code CONFLICTING_GROSS_PAY, citing R7 and R9.

Wait — but should I check the reference row first? R7's order: 1. Missing gross_pay — no, it's present. 2. Missing payroll_month — no, present. 3. Month without reference row — 2026-11 is in 2026, which is covered. But do I need to check the reference row? The month is 2026-11, which is within 2026, so a reference row exists. The check order in R7 lists the conflicting gross pay check as item 4. So the conflict check comes after the reference row check. Since 2026-11 is covered, we proceed to item 4, which triggers CONFLICTING_GROSS_PAY.

Actually, I don't even need to look up the reference since the conflict resolves to clarify before calculation. But the order of checks in R7: items 1-3 come before item 4. Item 3 requires knowing whether the month has a reference row. 2026-11 is in 2026, so covered by R1's statement "Only 2026 is covered." I could look up the reference to confirm, but the conflict is decisive regardless. Actually, to be safe and thorough, the conflict check would trigger anyway. Since the amendment is not approved, the conflict stands.

The answer format for clarify: decision, reason_code, clauses. Optional explanation string naming the unresolved blocker and asking for its resolution.

Clauses: R7 and R9.

Explanation: The contract gross pay (3731.24) differs from the payroll record gross pay (3730.24), and the amendment (3730.24, effective 2026-01) is not approved, so it cannot resolve the conflict under R9. Request an approved amendment or corrected records.

I should not include monetary fields for clarify cases. The allowed_deduction of 269.21 — per R4, when the month or applicable row is absent... but here the row exists; still, we don't calculate a payslip because of the conflict. R7 says "For these cases do not return calculated monetary fields."

So the final answer:

{
  "decision": "clarify",
  "reason_code": "CONFLICTING_GROSS_PAY",
  "clauses": ["R7", "R9"],
  "explanation": "..."
}

Do I need to verify the reference row exists for 2026-11? The check order matters: item 3 (no applicable reference) comes before item 4 (conflicting gross pay). Since 2026 is covered per R1, 2026-11 has a reference row. I could call lookup_reference to confirm, but it's not strictly necessary. The instructions say reference rows are available only through lookup_reference. To be thorough and confirm item 3 doesn't apply, I could look up second-half (2026-11 is in the second half). Let me do that to be safe — it confirms the month is covered, so the conflict is the blocker, not a missing reference row.

Actually, since the conflict check triggers clarification anyway, the lookup isn't needed for the final answer. But being careful: if the month had no reference row, the answer would be NO_APPLICABLE_REFERENCE instead. 2026-11 is within 2026, so per R1 it's covered. I'll do a quick lookup to confirm the row exists for 2026-11, ensuring the correct reason code ordering. Let me call lookup_reference with "second-half".

The reference row covers 2026-07 through 2026-12, so 2026-11 is covered. Item 3 of R7 does not apply.

Now item 4: contract_gross_pay (3731.24) differs from payroll gross_pay (3730.24). The amendment has gross_pay 3730.24, effective_month 2026-01 (no later than 2026-11), but approved = false. Per R9, an unapproved amendment does not resolve the conflict. Therefore: decision "clarify", reason_code "CONFLICTING_GROSS_PAY", clauses R7 and R9.

No calculated monetary fields. Include a short explanation naming the unresolved blocker and asking for its resolution.

Let me start by listing the documents and getting the reference tables.

There's a payroll record, a contract, and an amendment. Let me read all three documents, plus the reference tables. Since the payroll month determines which half of the reference table to use, I need to read the payroll first. But I can read all documents in parallel and both reference lookups in parallel too — actually the reference lookup depends on the payroll month. Let me read the documents first.

The payroll record:
- gross_pay: 3730.24
- payroll_month: 2026-11
- allowed_deduction: 269.21

Contract gross_pay: 3731.24 — differs from payroll gross_pay (3730.24).

Amendment: gross_pay 3730.24, effective_month 2026-01, approved: false.

R9: An amendment resolves a contract conflict only if it is approved, its effective month is no later than the payroll month, and its amount equals the payroll record's gross pay. Here the amendment is NOT approved, so it does not resolve the conflict.

R7.4: If optional contract_gross_pay is present and differs from gross_pay, neither source takes precedence unless an approved amendment resolves it under R9. Otherwise return decision: "clarify" and reason_code: "CONFLICTING_GROSS_PAY", citing R7 and R9.

Wait — but is the contract's gross_pay an optional `contract_gross_pay` field? The contract document has gross_pay 3731.24, and the payroll record has 3730.24. These differ. The amendment is not approved (approved: false), so it does not resolve the conflict. Therefore the answer is clarify with CONFLICTING_GROSS_PAY.

Hmm, but wait. Let me think carefully. The amendment amount (3730.24) equals the payroll record's gross pay (3730.24), and effective_month 2026-01 is no later than 2026-11. But approved is false. So it's a draft/unapproved amendment, which does not resolve a conflict per R9: "A draft, future, or different-amount amendment does not resolve a conflict."

So decision: clarify, reason_code: CONFLICTING_GROSS_PAY, citing R7 and R9.

The answer format: clarify uses decision, reason_code, clauses. Optional explanation string permitted. For clarification include a short explanation naming the unresolved blocker and asking for its resolution.

No monetary fields should be returned for clarify cases ("For these cases do not return calculated monetary fields").

So the JSON:
{
  "decision": "clarify",
  "reason_code": "CONFLICTING_GROSS_PAY",
  "clauses": ["R7", "R9"],
  "explanation": "The payroll record's gross pay (3730.24 LCR) conflicts with the contract gross pay (3731.24 LCR). The amendment matches the payroll amount and is effective 2026-01 (before the payroll month 2026-11) but is not approved, so under R9 it cannot resolve the conflict. Please provide an approved amendment or otherwise resolve the gross pay discrepancy."
}

I don't need to do any calculation or reference lookup since clarification is required before calculation. The check order in R7: 1. missing gross_pay — no. 2. missing payroll_month — no. 3. month without reference row — 2026-11 is in 2026, covered. 4. conflicting gross pay — yes, conflict unresolved.

So the answer is clarify. No need for lookup_reference or calculate.

Let me format the JSON without Markdown fences, no surrounding prose.