# Revision checks and evidence review

## Executed checks
- Original five submitted files archived byte-for-byte in `original_submission/`; SHA-256 hashes recorded and checked after revision.
- All five raw assignment/input files remained unchanged during revision (before/after SHA-256 comparison).
- Regenerated the current drafts using Python standard library with explicit UTF-8 file I/O; baseline checks passed (`checks.md`).
- Reopened and parsed the actual delivered CSV and Markdown: exact seven-column CSV schema, no missing/extra cells, all 10 tickets once and in input order, exactly one reply per ticket.
- All on-disk replies under 120 whitespace-delimited words, including source notes; counts below.
- Checked all decisions, priority labels and human-review flags against the reviewed expected matrix. Priority conventions remain disclosed assumptions, not additional policy.
- Checked all numeric refund cells with decimal arithmetic. Positive amounts equal their relevant merchandise amount; T703 is explicitly an alternative conditional refund, not a refund plus replacement. T708/T710 amounts remain intentionally blank.
- Checked each triage row and reply for policy/input citations and only its own order ID; all cited policy sections exist and agree between CSV and reply.
- Checked key conditions in actual drafts: T701 receipt/shipping; T703 photo/prepaid shipping; T704 exclusion of exactly 20%; T706 payment verification; T707 no bank-date promise; T708 no reconnection/testing and private contact; T710 privacy refusal.

## Evidence and requirement review
No conflicting supplied policy versions or order/payment values were found. The only unsupported override claim is the alleged manager approval in `inputs/tickets.csv`, T704; neither `inputs/orders.csv`, A704 nor `inputs/policy.md`, Returns/Evidence verifies an exception. The request to ignore policy remains rejected.

Date arithmetic and eligibility reviewed against `inputs/orders.csv` and `inputs/policy.md`, Returns/Defects and duplicates:
- A701: 30 days since September 20 delivery; inclusive deadline met, receipt/unopened condition still required; CAD 180 conditional.
- A702: 31 days since September 19 delivery; outside standard return window.
- A703: 5 days since October 15 delivery; damage-photo evidence missing, replacement preferred; CAD 60 refund alternative after photo verification.
- A704: 11 days since October 9 purchase, but 20% viewed excludes eligibility.
- A705: 12 days since October 8 purchase and 10% viewed; CAD 120 eligible.
- A706: two settled captures; one CAD 30 duplicate refund conditional on payment-team verification (`inputs/tickets.csv`, T706 supplies the reported charge amounts).
- A707: one settled capture plus one pending authorization; no duplicate refund (`inputs/tickets.csv`, T707 supplies the reported amounts).
- A708: 3 days since October 17 delivery; smoke/sparks require immediate human safety escalation regardless of refund eligibility (`inputs/tickets.csv`, T708; `inputs/policy.md`, Safety). No defect verification or compensation decision is claimed.
- A709: 12 days since October 8 delivery does not override the personalized-product change-of-mind exclusion (`inputs/tickets.csv`, T709).
- UNKNOWN: no matching order; do not infer an association with A701 or disclose others' information (`inputs/tickets.csv`, T710; `inputs/policy.md`, Safety/Evidence).

October 20 is the assessment/report date assumption for tickets lacking timestamps, disclosed in README. No operational action was taken or external verification performed. Negative statements about actions now explicitly refer to preparing the drafts rather than claiming knowledge of historical actions absent from the export. Manual content review found no cross-customer details, cause diagnosis, bank release-date promise, or compensation promise. Automated order-ID checks are narrower than full privacy review.

## On-disk reply word counts
- T701: 63
- T702: 54
- T703: 69
- T704: 72
- T705: 66
- T706: 68
- T707: 69
- T708: 79
- T709: 52
- T710: 82
