Let me start by listing the documents to get the case inputs.

Let me read both documents.

The payroll record has gross_pay 9728.06 and payroll_month 2026-02. The contract has gross_pay 9703.06, which differs from the payroll gross_pay. There's no amendment in the documents. Wait — R7 item 4 says: "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."

Hmm, but wait. Let me think carefully. The contract gross pay differs from payroll gross pay. Is there an amendment? The documents list only payroll and contract. No amendment document. So the conflict is unresolved → clarify with CONFLICTING_GROSS_PAY, citing R7 and R9.

Wait, but let me double check — maybe the contract is not "optional contract_gross_pay" in the task input sense. The rule says "If optional `contract_gross_pay` is present and differs from `gross_pay`". Here the contract document has gross_pay 9703.06, which differs from payroll's 9728.06. There's no amendment. So we return clarify.

Actually, let me be careful. Should I check the reference tables first? The month 2026-02 is covered (only 2026 is covered). But the conflict check happens in order: 1. missing gross_pay — no. 2. missing payroll_month — no. 3. month without reference row — 2026-02 is covered. 4. conflicting gross pay — yes, contract differs, no amendment → clarify.

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

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

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

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

Wait, but should I double-check whether the contract is considered "present"? The contract document exists with gross_pay 9703.06, differing from payroll's 9728.06. Yes.

Hmm, but one thing: is there possibly an amendment embedded somewhere? The list_documents only showed two documents, both read. No amendment. So conflict unresolved.

Do I need lookup_reference? Not needed since we're clarifying before calculation. The conflict check (item 4) comes after reference row check (item 3), but 2026-02 has a reference row presumably. Actually, I should verify that 2026-02 has a reference row — if it didn't, item 3 would trigger first with NO_APPLICABLE_REFERENCE. Only 2026 is covered per R1, and 2026-02 is in 2026, so it should be covered. But to be safe, I could do a lookup_reference to confirm the month is covered. The instructions say reference rows are available only through lookup_reference. Since the check order requires confirming a reference row exists before the conflict check, let me do a lookup to confirm 2026-02 is covered. First-half covers months 1-6 presumably. Let me call lookup_reference first-half.

Actually, the order of checks: 1, 2, 3, 4. Item 3: "A month without a reference row". 2026-02 — I should confirm there's a row. Let me call lookup_reference("first-half") to verify. That's a reasonable step.

Then return the clarify answer.

The first-half reference covers 2026-01 through 2026-06 (months listed as ["2026-01", "2026-06"] — presumably a range from 2026-01 to 2026-06). So 2026-02 is covered.

Check order:
1. Missing gross_pay? No — 9728.06 present.
2. Missing payroll_month? No — 2026-02 present.
3. Month without reference row? No — 2026-02 covered by first-half row.
4. Contract gross pay present (9703.06) and differs from payroll gross_pay (9728.06). No amendment exists to resolve it. → clarify, CONFLICTING_GROSS_PAY, citing R7 and R9.

The difference: 9728.06 vs 9703.06 — differs by 25.00. No amendment document. So clarify.

Return JSON:
{
  "decision": "clarify",
  "reason_code": "CONFLICTING_GROSS_PAY",
  "clauses": ["R7", "R9"],
  "explanation": "The payroll record's gross pay (9728.06 LCR) conflicts with the contract's gross pay (9703.06 LCR) for 2026-02, and no approved amendment resolves the conflict. Please provide an approved amendment (effective by 2026-02, matching amount) or a corrected source."
}

No monetary calculated fields. Money must be strings with two decimals — the amounts in the explanation are fine as text; but the rule says "Money must be strings with two decimal places" — in explanation prose I'll write them as 9728.06 and 9703.06 which is fine.

Return one JSON object without Markdown fences or surrounding prose.

Let me start by listing the documents to get the case inputs.

Let me read both documents.

Payroll record: gross_pay = 9728.06, payroll_month = 2026-02. Contract gross_pay = 9703.06, which differs from the payroll record's gross_pay.

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 clarify with reason_code CONFLICTING_GROSS_PAY, citing R7 and R9.

Is there an amendment? No amendment document was provided. So the conflict is unresolved → clarify.

Wait — but let me double-check the contract. The contract is a document with gross_pay 9703.06. The payroll record has gross_pay 9728.06. These differ. There's no amendment. So decision: clarify, reason_code: "CONFLICTING_GROSS_PAY", clauses: R7, R9.

The answer fields for clarify: decision, reason_code, clauses. An optional explanation string is permitted. Do not include calculated monetary fields or input-only fields like contract_gross_pay.

So the answer:

{
  "decision": "clarify",
  "reason_code": "CONFLICTING_GROSS_PAY",
  "clauses": ["R7", "R9"],
  "explanation": "The payroll record's gross_pay (9728.06 LCR) differs from the contract's gross_pay (9703.06 LCR) for 2026-02, and no approved amendment resolves the conflict. Please provide an approved amendment effective no later than 2026-02 whose amount matches the payroll record's gross pay."
}

Should I include the amounts in the explanation? The rules say "Do not include input-only fields such as payroll_month, contract_gross_pay, or amendment." That refers to fields, not explanation text. The explanation should name the unresolved blocker and ask for its resolution. Mentioning the values in prose should be fine, but to be safe I could keep it brief. Actually, naming the blocker clearly is required. I'll mention the conflict without necessarily listing exact figures... Actually including figures in the explanation helps clarity. The rule says fields must not include input-only fields; the explanation is prose. I'll include the conflict description.

Let me also verify there's no need for lookup_reference — since we're clarifying, no calculation is needed. The month 2026-02 is covered, but the blocker is the gross pay conflict, which is checked at step 4 after the reference row check (step 3). Since the month has a reference row (2026 covered), we proceed to step 4 and hit the conflict. No need to look up reference values since we don't calculate.

Answer format: one JSON object without Markdown fences or surrounding prose.

Let me start by listing the documents to get the case inputs.

Payroll: gross_pay = 9728.06, payroll_month = 2026-02. Contract gross_pay = 9703.06, but there's no amendment document. Contract differs from payroll gross pay. 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 clarify with CONFLICTING_GROSS_PAY.

Wait — but is the contract's gross_pay "optional contract_gross_pay" present? The contract document exists with gross_pay 9703.06, differing from payroll 9728.06. There's no amendment. So this is a conflicting gross pay situation → clarify with reason_code CONFLICTING_GROSS_PAY, citing R7 and R9.

Hmm, but wait — should I check the reference tables first? 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 the conflict check comes after the reference row check. 2026-02 is covered by 2026 rows (only 2026 is covered). Let me verify with lookup_reference to be safe — actually, the rules say reference rows are available only through lookup_reference. Since decision is clarify, do I need the reference? The order says check month coverage before conflict. 2026-02 — only 2026 is covered, and the default reference presumably covers all of 2026. But there might be a case schedule. Let me check lookup_reference to confirm 2026-02 has a row. The lookup tool has first-half and second-half options — probably first-half covers Jan-Jun, second-half Jul-Dec.

Let me call lookup_reference for first-half to confirm 2026-02 is covered. Actually, since the conflict check (step 4) comes after the month check (step 3), I should verify the month has a reference row before returning CONFLICTING_GROSS_PAY. Let me do that.

Also, should I check whether there's an amendment? The list_documents only showed payroll and contract — no amendment document. So no amendment exists.

So the answer: decision clarify, reason_code CONFLICTING_GROSS_PAY, clauses R7 and R9, with a short explanation naming the unresolved blocker and asking for its resolution.

Let me still verify the reference row for 2026-02 exists (step 3 before step 4). Call lookup_reference first-half.

The first-half reference covers 2026-01 through 2026-06, so 2026-02 has a reference row. Step 3 passes. Step 4: contract gross_pay 9703.06 differs from payroll gross_pay 9728.06. No amendment document exists (list_documents showed only payroll and contract). So the conflict is unresolved → clarify with reason_code CONFLICTING_GROSS_PAY, citing R7 and R9.

Per the rules: "For these cases do not return calculated monetary fields." So the answer JSON: decision: "clarify", reason_code: "CONFLICTING_GROSS_PAY", clauses: ["R7", "R9"], plus a short explanation naming the unresolved blocker and asking for its resolution.

Output must be one JSON object without Markdown fences or surrounding prose.