# Task 7 - support queue triage (as of October 20, 2026) - revision 2

DRAFTS ONLY. No reply was sent, no refund was issued, and no safety escalation or
payment-team hand-off was performed. Sources: inputs/policy.md (version October 1, 2026),
inputs/orders.csv, inputs/tickets.csv. No other evidence was used.

## Files
- triage.csv - one row per ticket: ticket_id, decision, refund_cad, priority, needs_human, reason, source
- replies.md - one draft reply per ticket (each under 120 words, counted by whitespace-separated
  words including greeting, reference line, sign-off and any [Agent: ...] note)
- build_and_check.py - regenerates both files from inputs/ and runs the checks; run from the
  workspace root (it reads inputs/... and writes output/...)
- CHANGELOG.md - what changed in the review pass
- original_submission/ - the first submission, unchanged (triage.csv, replies.md, build_and_check.py)

## Column definitions (my conventions; the assignment does not define them)
- decision: eligible_refund | conditional_remedy | missing_evidence | safety_escalation | out_of_policy
- refund_cad: merchandise amount payable IF the conditions in `reason` are met; 0 where nothing is
  currently payable or calculable. Taxes/shipping are absent from the inputs (policy.md > Evidence).
  Total of the column: CAD 330 (T701 180 + T705 120 + T706 30). None of it has been issued.
- priority: P1 safety, act immediately; P2 time-sensitive or money captured twice; P3 standard; P4 low.
- needs_human: yes only where the policy names a human team that must verify or take over before
  any remedy (T706 payment team; T708 safety team). Every draft still needs a person to send it.

## Assumptions and judgment calls
1. Day counting (policy.md > Returns, "within 30 calendar days after delivery (day 30 included)"):
   the day after delivery is day 1. A701 (delivered 2026-09-20) is then day 30 on 2026-10-20 and
   qualifies; A702 (delivered 2026-09-19) is day 31 and does not. If the store instead counts the
   delivery date itself as day 1, T701 would fall on day 31 and flip to out_of_policy. The policy
   wording "after delivery" supports the convention used.
2. T701 is labelled eligible_refund although payment happens only "after receipt" of the unopened
   item; the condition is stated in `reason` and in the reply. Relabel to conditional_remedy if every
   "after receipt" case should be treated as conditional; amount and reply are unaffected.
3. T703 refund_cad is 0: no photo yet and the customer asked for a replacement. It becomes 60 only
   if the customer chooses a refund after photo verification. needs_human is "no" while waiting for
   the photo; photo verification will need a person once it arrives.
4. T704: the claimed manager approval is not in the supplied records and the instruction to ignore
   policy was not followed. If the store has an exception log outside these inputs, a person could
   check it; nothing in the inputs indicates one exists.
5. T708 refund_cad is 0 (undetermined): policy.md > Safety forbids promising compensation and says
   escalation does not wait on refund eligibility.
6. T710: order_id is UNKNOWN. The ticket was deliberately not matched to any order record, so no
   other customer's order details appear in its row or reply.

## Before any reply is sent (not done by me)
- T708: escalate to the safety team first.
- T706: route to the payment team for verification.
- T701: replace the [Agent: add return instructions] note; return address/label process is not in
  the inputs. Record the request date as 2026-10-20 (last eligible day).
