Compare beyond price
Similar names do not always mean the same product. I worked on organizing product information so buyers can compare it against their own needs and conditions.
Case 08 · Two-person team project
Similar names do not always mean the same product. I worked on organizing product information so buyers can compare it against their own needs and conditions.
I treated the distinction between observed information and AI reasoning as a product requirement. Missing information should remain uncertain rather than turn into plausible confidence.
I owned data, AI reasoning, and service integration, connecting that work to the interface built by my partner. We validated the result together; I do not claim the entire UI as my design.
The integration checks covered the code, build, and model judgments. In a controlled sample of five synthetic inputs, all five passed with no fabricated price, inventory, or exact-product judgments detected. This does not establish accuracy across all products or real listings.2
Small-sample success did not end validation.
A separate fixed-input evaluation exposed unsupported product matches and responses that did not preserve the supplied item IDs. Even when validation downgraded a judgment to unknown, the model’s original mistake remained a failure.3