# Review and change log

## Outcome

The original arithmetic, conflict resolution and selection were correct. O2 remains the recommendation at CAD 2,098.88 landed, with CAD 101.12 budget headroom. No new source evidence, purchase, delivery confirmation or hardware benchmark was obtained.

## Revisions

- Preserved the two original deliverables byte-for-byte in `output/original_submission/` before editing.
- Made the GPU interpretation more precise in `recommendation.md`: S1 lists GPU models and VRAM but has no explicit discrete/integrated classification. The recommendation is conditional on treating the listed GX GPUs as discrete; this is not a newly verified specification. The original already stated this interpretation, but did not spell out the missing source field.
- Added `listing_note`, `gpu_type_basis` and `hardware_pass_basis` columns to `comparison.csv`, preserving the original listing conflicts and making the GPU assumption visible when the CSV is used alone. No prices, totals, delivery outcomes or offer rankings changed.
- Explicitly attributed the export result to the supplied lab note, rather than leaving room to read it as a test performed for this submission. Corrected punctuation in the S3 heading citation.

## Checks actually performed

- Re-read the assignment and all five supplied input files; compared both deliverables with the source register's authority rules.
- Recalculated all six taxable subtotals, taxes, landed totals and budget headroom with Python `Decimal`; verified them against the original CSV. Landed totals O1–O6: CAD 2,238.88; 2,098.88; 1,790.88; 1,902.88; 2,126.88; 2,037.28.
- Compared each CSV SKU, model, RAM, SSD, GPU, VRAM, weight and OS with `inputs/S1-manufacturer-specs.csv`, corresponding SKU records; compared each store, price, shipping and original delivery with `inputs/S2-store-offers.csv`, O1–O6.
- Verified hard gates under the disclosed GPU interpretation: O1 over budget; O3 insufficient RAM/SSD despite title; O4 insufficient VRAM despite title; O5 estimated arrival is not a commitment; O6 corrected to October 27 with no expedited service; only O2 passes. Sources: `inputs/00-source-register.md`, “Scenario sources — captured October 19, 2026, 09:00 Pacific”; `inputs/S3-store-correction.md`, “S3 — Direct Aspen correction — October 19, 2026, 08:45 Pacific,” O6/A15-32; S1/S2 records cited above.
- Checked the lab-result wording against `inputs/S4-independent-test.md`, “S4 — Edit Bench lab note — October 17, 2026”: one plugged-in F16-32 run, 12-minute UHD H.264 timeline, 8:40 export, noticeable fans; no comparative or broader-workload claims.
- Reopened the revised UTF-8 CSV with Python's CSV reader: six unique offers, consistent columns, no missing cells or extra-field parsing errors. No spreadsheet GUI or rendered Markdown test was performed.
- Checked recommendation length: **541 whitespace-delimited words**, below 650. Compared original archive bytes and verified that all input-file hashes were unchanged during this review.

## Handoff and limitations

Revised files: `output/recommendation.md`, `output/comparison.csv`. Originals: `output/original_submission/recommendation.md`, `output/original_submission/comparison.csv`. Review record: `output/change_log.md`.

No new confirmation of discrete GPU classification or O5 delivery exists in the packet. The fallback remains a proposed request for a binding delivery commitment, not an already qualifying alternative. Performance evidence remains limited to the supplied single run. The deliverables are complete for the scenario; estimated human time is **3–5 minutes** to review the revisions (an estimate, not a measured duration). Any seller clarification or purchase would be a separate action with unknown response time.
