Gemini 3.7 Flash · Google ADK · Cloud Run
A recall on something you own is announced to a government database, not to you. Keep registers your possessions once, watches three federal feeds while you are away, and pursues the remedy when one lands.
A household owns a Yeti Rambler tumbler. CPSC recall 26712 covers the Goal Zero YETI 3000X power station. The recall text really does say YETI. A matcher built on brand tokens flags the tumbler, the owner learns the alerts are noise, and the product is dead on its first screenshot.
The rule, in one sentence: an exact identifier, or brand and model agreeing, or a distinctive model number on its own — and nothing else. A lone brand match never qualifies.
A deterministic prefilter applies that rule to narrow thousands of pairs to a handful; Gemini then adjudicates the shortlist and returns a verdict, a confidence and a reason. The prefilter never flags and the model never sweeps. Every refusal is logged with its reason and drawn in the scene with exactly the weight a hit gets, because it is the more interesting of the two answers.
Cloud Scheduler fires a Cloud Run Job every hour. It pulls the feeds, decides, opens claims and writes to Firestore with nobody present — and the execution history is the evidence. There is no chat interface anywhere in this project.
On a match the Claimant determines the remedy, drafts a claim citing the specific campaign, sends it, and re-enters on a schedule to escalate — consumer line, then compliance, then the regulator. Statute citations come from a fixed table and never from the model.
No seeded recalls, ever. Every recall ID in the scene links to the government page it came from, and the row counts the sweep animation is drawn from are the real ones.
| CPSC | consumer product recalls | 9,966 records, refreshed daily |
|---|---|---|
| NHTSA | vehicle campaigns | VIN decoded through vPIC, then by make/model/year |
| openFDA | food and drug enforcement | answers an empty window with HTTP 404 |
global endpoint, no API key — the services reach it with their own credentialsinclude_thoughts on the planner