# Task 7 notes - assumptions, limitations and change log (revision 2)

Drafts only. No reply was sent, no refund issued, no escalation filed.
The first submission is preserved unchanged in output/original_submission/.

## Assumptions
- tickets.csv has no date column, so every ticket is treated as received on 2026-10-20 (the "as of" date in the task; T701 states it explicitly).
- policy.md is headed "version October 1, 2026". Orders A701 (purchased 2026-09-10) and A702 (purchased 2026-09-12) predate that version. It is applied to them anyway because it is the only policy supplied and the task says to use it. This matters most for T702, which is declined by one day; whether different terms applied at purchase cannot be checked from the inputs.
- Day counts are calendar days from delivery (or purchase, for digital courses) to 2026-10-20: A701 = 30, A702 = 31, A703 = 5, A704 = 11, A705 = 12, A708 = 3, A709 = 12.
- `needs_human` = yes only where policy.md names a human team that must act before the case can progress now (payment team for T706, safety team for T708). Every refund still needs a person to release it, because this is draft-only. T703 will need a person to verify the photo once the customer sends it.
- `refund_cad` is the merchandise amount that is due or conditionally due. T703 is 0 because the customer asked for a replacement; it becomes 60 only if they choose a refund after photo verification. T708 is 0 because policy.md, Safety, says not to promise compensation.
- T710 is not matched to order A701, even though that is the only headphones order in orders.csv: the ticket's order ID is UNKNOWN and matching by item would risk exposing another customer's order.
- T704: the claimed manager approval is not in the supplied records and policy.md has no exception route, so it is declined rather than routed to a human.

## Limitations
- "Sealed", "unopened", "cracked" and statement contents are customer claims; nothing was inspected (policy.md, Evidence).
- Taxes and shipping are absent, so only merchandise amounts are stated (policy.md, Evidence).
- The inputs contain no return address, return-label process or contact channel, so the replies for T701, T703 and T708 do not include them.
- The T708 reply says the report "is being escalated"; that is only true once a person files the escalation before sending.

## Change log (revision 2 vs original_submission)
1. Added the policy-version assumption (policy dated 2026-10-01 applied to September purchases A701 and A702) to this file and to the T701 and T702 reasons in triage.csv. It was missing from the first submission. No decision changed.
2. replies.md: added an internal "Source:" line under each reply naming the input file, section heading and record IDs. The first version cited only the policy section and order inside the reply text.
3. replies.md T704: "the records available to me show no approved exception" changed to "I have no record of an approved exception", because the supplied records have no approvals field at all.
4. triage.csv and replies.md are now ASCII-only ("section" instead of the section sign, hyphen instead of em dash) so the CSV opens cleanly in spreadsheet tools without encoding settings.
5. triage.csv: T703 reason notes that a person must verify the photo later; T708 reason notes the escalation is not yet filed.
6. No decision, refund amount, priority or needs_human value changed.
