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

The payroll month is 2027-05. According to R1, only 2026 is covered. Dates outside 2026 require clarification under R7. So this should be a clarify with reason_code "NO_APPLICABLE_REFERENCE", citing R1 and R7.

Wait, but let me check: R7 order:
1. Missing gross_pay — no, gross_pay is present.
2. Missing payroll_month — no, present.
3. A month without a reference row: return clarify with NO_APPLICABLE_REFERENCE, citing R1 and R7. Do not extrapolate an old row.

2027-05 is outside 2026, so no reference row applies. Decision: clarify, reason_code: NO_APPLICABLE_REFERENCE, clauses R1 and R7.

Also note R4's 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." The allowed_deduction of 339.95 — structurally valid (non-negative, two decimals). But we don't calculate a payslip.

Also R2: money values valid (4390.15, 339.95 — fine).

Should I check lookup_reference to confirm 2027-05 has no row? The reference tables only cover 2026 per R1. The instructions say reference rows are available only through lookup_reference. I could call lookup_reference to verify there's no row for 2027-05. Let me do that to be thorough — check both halves. Actually, the rules say only 2026 is covered, so 2027-05 has no row regardless. But to be safe and follow the instruction "Reference rows are available only through lookup_reference", I could call it. It's not strictly necessary since the month is outside 2026. But calling to confirm doesn't hurt. Let me call both first-half and second-half lookups in parallel to confirm coverage.

Actually, the R7 check order says: missing gross_pay (no), missing payroll_month (no), month without reference row → clarify NO_APPLICABLE_REFERENCE. The month 2027-05 is outside 2026. R1 says "Dates outside 2026 require clarification under R7."

I'll do a quick lookup to confirm no row exists for 2027-05.

Confirmed: reference rows cover only 2026-01 through 2026-12. The payroll month 2027-05 has no applicable reference row. Per R1 and R7, return clarify with reason_code NO_APPLICABLE_REFERENCE.

Do not calculate monetary fields. The allowed_deduction 339.95 is structurally valid but no payslip is calculated.

Output JSON:
{
  "decision": "clarify",
  "reason_code": "NO_APPLICABLE_REFERENCE",
  "clauses": ["R1", "R7"],
  "explanation": "..."
}

The explanation should name the unresolved blocker and ask for resolution.

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

The payroll month is 2027-05. Rules say only 2026 is covered. Dates outside 2026 require clarification under R7. So the answer should be clarify with reason_code "NO_APPLICABLE_REFERENCE", citing R1 and R7.

Wait, let me check the order of checks in R7:
1. Missing gross_pay — present (4390.15).
2. Missing payroll_month — present (2027-05).
3. A month without a reference row — 2027-05 has no reference row since only 2026 is covered. Return clarify with NO_APPLICABLE_REFERENCE.

Also allowed_deduction is present (339.95), structurally valid. R4 says when the month is absent, accept structurally valid deductions up to the largest reference deduction cap for task validation, but do not calculate a payslip. So clarify.

I could optionally verify via lookup_reference, but the rulebook says only 2026 is covered. The lookup_reference tool reads first-half or second-half reference rates. Let me check whether the schedule covers 2027. The rules say "Only 2026 is covered." But maybe the case has an authoritative reference_tables schedule. R1 says "A case may include an authoritative reference_tables schedule for first-half and second-half. When supplied, its numeric values replace the defaults above for that case only." In tool mode this schedule is available only through lookup_reference. So I should check lookup_reference to see if the schedule covers 2027-05.

Let me call lookup_reference for first-half and second-half in parallel to see the coverage.

The reference rows cover only 2026-01 through 2026-12. The payroll month 2027-05 has no reference row. Per R7 item 3, return decision "clarify" with reason_code "NO_APPLICABLE_REFERENCE", citing R1 and R7.

The allowed_deduction 339.95 is structurally valid (non-negative, two decimals) and under the largest reference deduction cap (400.00), so it's accepted for task validation, but no payslip is calculated.

Return JSON without markdown fences, only required fields: decision, reason_code, clauses. Optional explanation string naming the unresolved blocker.

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

The payroll month is 2027-05. Rules say only 2026 is covered. Dates outside 2026 require clarification under R7. Also, I should check the reference tables via lookup_reference — but the month is 2027-05, outside 2026. Per R1: "Only 2026 is covered. Dates outside 2026 require clarification under R7." And R7 item 3: a month without a reference row → clarify with reason_code "NO_APPLICABLE_REFERENCE", citing R1 and R7.

But wait — should I check lookup_reference to confirm? The rules say reference rows are available only through lookup_reference. There might be a case schedule. Let me check both halves to see if there's a schedule covering 2027. Actually, R1 says "A case may include an authoritative reference_tables schedule for first-half and second-half. When supplied, its numeric values replace the defaults above for that case only." The schedule is available only through lookup_reference. Let me look it up to see whether 2027-05 has a row.

The defaults cover 2026 only. If the schedule also only covers 2026, then 2027-05 has no applicable reference → clarify NO_APPLICABLE_REFERENCE.

Let me call lookup_reference for both halves in parallel to verify.

The reference rows cover only 2026 (first-half: 2026-01 through 2026-06; second-half: 2026-07 through 2026-12). The payroll month is 2027-05, which has no applicable reference row. Per R7 item 3, return clarify with reason_code "NO_APPLICABLE_REFERENCE", citing R1 and R7.

The record has gross_pay and allowed_deduction present. The blocker is the payroll month 2027-05 being outside coverage. No calculated monetary fields should be returned.

Answer format: decision "clarify", reason_code "NO_APPLICABLE_REFERENCE", clauses ["R1", "R7"], plus optional explanation. Money fields should not be included.