# Processing notes — Task 7 support queue (as of 2026-10-20) — revision 2

## Scope and status
- All 10 tickets in inputs/tickets.csv processed against inputs/policy.md (version October 1, 2026) and inputs/orders.csv only.
- DRAFT ONLY: no replies sent, no refunds issued, no replacements ordered, no payment reversals, no escalation actually executed. T708 is flagged for immediate human safety escalation in triage.csv.
- Raw inputs preserved untouched; deliverables are output/triage.csv and output/replies.md. Revision-2 wording corrections are listed in output/changelog.md; the original submission is preserved in output/original_submission/.

## Decision vocabulary
- eligible_refund: policy conditions met on supplied records (T701, T705). For physical goods the refund is still payable only after the return is received (policy ## Returns); receipt has not occurred.
- conditional_refund: refund amount calculable but gated on verification not yet performed (T706, payment-team verification per ## Defects and duplicates).
- missing_evidence: cannot decide without customer-supplied evidence (T703 photo; T710 order identification).
- safety_escalation: T708 (smoke/sparks) — highest priority, human-only per ## Safety.
- out_of_policy: no remedy available under policy (T702 window expired; T704 20% viewed excluded; T707 pending authorization is not a second charge; T709 personalized change-of-mind).

## refund_cad convention
Merchandise-only amounts (taxes/shipping absent per ## Evidence). 0 means no refund determined yet, not a verified denial of any future amount: T703 could become CAD 60 after photo verification if refund (not replacement) is chosen; T708 has no amount promised per ## Safety. Total currently calculable: 180 + 120 + 30 = CAD 330, all pending processing/verification.

## needs_human convention
true = requires human verification, judgment or action beyond routine processing (receipt inspection T701; photo review T703; claimed manager approval T704; payment team T706; safety team T708; order lookup T710). false = decision fully determined by supplied records (routine issuance for T705 still performed by staff, since this is a draft).

## Date calculations (verified by script, work/build_and_check.py; re-run in review)
- A701: delivered 2026-09-20 → 2026-10-20 = day 30 (included) → eligible.
- A702: delivered 2026-09-19 → day 31 → outside window.
- A703: delivered 2026-10-15 → day 5 ≤ 7 → damage process applies, photo missing.
- A704: purchased 2026-10-09 → day 11 ≤ 14, but course_viewed_pct = 20 (20% excluded) → denied.
- A705: purchased 2026-10-08 → day 12 ≤ 14, viewed 10% < 20% → eligible.
- A708: delivered 2026-10-17 → day 3; safety takes precedence, eligibility not assessed.
- A709: delivered 2026-10-08 → day 12; personalized exclusion applies regardless.

## Assumptions (inputs do not resolve these)
1. "Today" in customer messages = 2026-10-20, the stated processing date.
2. Customer claims of "unopened"/"sealed" (T701, T702) and viewing percentages are taken as claims; order records corroborate viewing pct for A704/A705. Physical condition is unverified until receipt.
3. T704's claimed manager approval has no record in supplied inputs; treated as unverified, not honored. needs_human=true so a supervisor can review any written approval the customer supplies.
4. T706: orders.csv settled_captures=2 is treated as the record of two captures on the CAD 30 order; the CAD 30-per-charge amount is the customer's claim. Refund still conditional on payment-team verification per policy.
5. T710 "headphones" cannot be matched to A701 or any order; no assumption made about which order it is. Other-customer information request refused (## Safety: never disclose other customers' information).
6. Priority scale urgent/high/medium/low is an analyst convention; policy only mandates "highest-priority" for safety.

## Checks actually performed (script output, exit 0; re-run after revision)
- Date deltas recomputed from inputs/orders.csv and asserted (values above).
- Record fields asserted: A704=20%, A705=10%, A706 two settled captures, A707 one settled + one pending, UNKNOWN absent from orders.
- triage.csv round-trip parsed: exact header, 10 rows covering T701–T710 in ticket order, valid decision/priority/needs_human values, integer refund_cad, policy+order citations in every source cell.
- replies.md: exactly 10 replies, one per ticket in order; word counts 69–92 (all < 120).
- Privacy scan: no reply body contains any order ID other than its own ticket's order.
- Preservation: output/original_submission/ copies SHA-256-match the pre-review files; revised triage.csv is byte-identical to the original.

## Second-pass review (revision 2)
Reviewed calculations, source conflicts, requirement coverage, file usability and action/test claims. Three wording corrections in replies.md (T706 evidence attribution, T706 removed implied completed queueing action, T707 removed prediction of bank/authorization outcome); see output/changelog.md. triage.csv and all decisions unchanged. No source conflicts found between tickets and orders.csv.

## Limitations
- No inspection, photo review, payment-team verification, bank data, return receipt, or manager-approval record exists in the inputs; those steps remain outstanding and are marked conditional/missing_evidence rather than completed.
- Taxes and shipping are absent from the export; only merchandise amounts are calculable (policy ## Evidence).
- No replies were sent and no system actions taken; a human must execute issuance, escalation (T708 first), verification and follow-up.
- No web research or external tools used; none needed for this task.
