Let me start by listing the documents to see what case inputs we have.

Let me read the payroll document.

The payroll record has:
- gross_pay: "3362.67"
- allowed_deduction: "72.10"
- No payroll_month!

Wait, let me check again. The record has gross_pay and allowed_deduction, but no payroll_month. Hmm, but wait — maybe there's more in the document. Let me re-read... The document shows only `{"kind": "payroll", "record": {"gross_pay": "3362.67", "allowed_deduction": "72.10"}}`.

So payroll_month is missing. According to R7:
1. Missing gross_pay → MISSING_GROSS_PAY
2. Missing payroll_month → MISSING_PAYROLL_MONTH
3. Month without reference row → NO_APPLICABLE_REFERENCE
4. Conflicting gross pay → CONFLICTING_GROSS_PAY

Order matters: check missing gross_pay first, then missing payroll_month. Gross pay is present ("3362.67"). Payroll_month is missing → clarify with reason_code "MISSING_PAYROLL_MONTH", citing R1 and R7.

The clarification answer fields: decision, reason_code, clauses. Optional explanation string. No monetary fields.

Should I double check whether the document might contain more? The read_document returned the full document. There's no payroll_month. So the answer is clarify.

Let me make sure I don't need lookup_reference — since payroll_month is missing, no reference row can be selected. The clarification is straightforward.

Format: one JSON object, no Markdown fences, no surrounding prose. Fields: decision: "clarify", reason_code: "MISSING_PAYROLL_MONTH", clauses: ["R1", "R7"], explanation naming the unresolved blocker.

The instructions say "For clarification include a short explanation naming the unresolved blocker and asking for its resolution." So include explanation.

Also "Missing required values include explicit null." — Hmm, that's for calculate cases with missing required values? Actually R7 says "For these cases do not return calculated monetary fields. Missing required values include explicit null." But the answer format for clarify only allows decision, reason_code, clauses (plus optional explanation). The instruction says "Use exactly the required answer fields and only the clauses that directly govern the answer." Allowed answer fields for clarify: decision, reason_code, clauses. So I should not add null fields. The "explicit null" guidance in R7 seems to apply to calculated answers where required values are missing — but clarify cases don't return monetary fields anyway. I'll stick to the allowed fields.

Final answer:

{"decision": "clarify", "reason_code": "MISSING_PAYROLL_MONTH", "clauses": ["R1", "R7"], "explanation": "The payroll record supplies gross_pay (3362.67) and allowed_deduction (72.10) but omits payroll_month, which R1 requires..."}

Wait — should I mention gross_pay in explanation? It's fine as explanation text, not an input-only field. The rule says "Do not include input-only fields such as payroll_month, contract_gross_pay, or amendment." That means don't add them as JSON fields; mentioning in explanation should be acceptable. To be safe, keep the explanation brief and mention that payroll_month is missing.

No need for calculate or lookup_reference calls. I already have everything needed.

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

The payroll record has gross_pay "3362.67" and allowed_deduction "72.10", but no payroll_month. According to R7, step 2: Missing payroll_month → decision: "clarify", reason_code: "MISSING_PAYROLL_MONTH", citing R1 and R7.

Let me double-check: the record has gross_pay and allowed_deduction only. No payroll_month field. So R7 order: 1. Missing gross_pay? No, gross_pay is present. 2. Missing payroll_month? Yes → clarify with MISSING_PAYROLL_MONTH.

I should not need lookup_reference or calculate. The answer format for clarify: decision, reason_code, clauses, optional explanation.

Return JSON without Markdown fences. Fields: decision: "clarify", reason_code: "MISSING_PAYROLL_MONTH", clauses: ["R1", "R7"], plus explanation naming the unresolved blocker and asking for resolution.

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

The payroll record has gross_pay = "3362.67" and allowed_deduction = "72.10", but no payroll_month. Per R7, missing payroll_month → clarify with reason_code "MISSING_PAYROLL_MONTH", citing R1 and R7.

Wait — check the order: 1. Missing gross_pay? No, gross_pay is present. 2. Missing payroll_month? Yes. So clarify with MISSING_PAYROLL_MONTH.

Also note there's no contract_gross_pay conflict. The record lacks payroll_month entirely. So the answer is clarify.

The allowed deduction is present but structurally valid? R4 says 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. Anyway, we must clarify.

For clarification: decision "clarify", reason_code "MISSING_PAYROLL_MONTH", clauses citing R1 and R7. Include a short explanation naming the unresolved blocker and asking for its resolution. No monetary fields. Missing required values include explicit null — but for clarify, the fields are decision, reason_code, clauses. The instruction "Missing required values include explicit null" applies to cases where we'd return calculated fields; for clarify we don't return monetary fields per R7 ("For these cases do not return calculated monetary fields").

So output JSON:
{"decision": "clarify", "reason_code": "MISSING_PAYROLL_MONTH", "clauses": ["R1", "R7"], "explanation": "..."}

Should I include explanation? Optional. Yes, include a short explanation naming the blocker and asking for resolution.

No need for lookup_reference or calculate since we can't determine the month. The blocker is missing payroll_month.