Dataset card: Into the Unknown, concise, current links

README.md

@@ -1,5 +1,5 @@
 ---
-pretty_name: Shoulders of Giants
+pretty_name: Into the Unknown
 license: other
 license_name: mixed
 license_link: LICENSE
@@ -17,52 +17,69 @@ configs:
   data_files: trajectories/index.csv
 ---
 
-# Shoulders of Giants
+# Into the Unknown
 
-**Can AI agents build on a scientist's work and write a follow-up paper?** Each of the 15 tasks gives an agent a
-published (or recently submitted) scientific paper and a follow-up research direction proposed by the paper's own
-author. The agent has to carry out the research and write the follow-up paper. Code, rubrics and graders:
-[GitHub](https://github.com/prometheus-eval/national-lab-bench). Leaderboard and every judge verdict:
-[website](https://prometheus-eval.github.io/national-lab-bench/).
+**Dataset Summary**
 
-## Subsets
+Into the Unknown tests whether AI agents can build on a scientist's work and write a follow-up paper. Each of its 15 tasks gives an agent a published (or recently submitted) paper and a follow-up research direction proposed by the paper's own author; the agent must carry out the research and write a follow-up paper that is honest, complete, and meets the scientist's bar.
 
-| Subset | Content |
+This dataset holds the 15 tasks and everything nine agents produced on them: 135 submissions, with each agent's paper, full trajectory, and the files it wrote. Code, rubrics and graders are on [GitHub](https://github.com/prometheus-eval/into-the-unknown); the paper is coming soon.
+
+**Supported Tasks and Leaderboards**
+
+The task is open-ended research: given the paper and the direction, produce the follow-up paper. The [leaderboard](https://prometheus-eval.github.io/into-the-unknown/viewer/#/) shows every agent's results and every rubric verdict, and you can [submit your agent's paper](https://prometheus-eval.github.io/into-the-unknown/viewer/#/submit) to be evaluated.
+
+**Subsets**
+
+| subset | content |
 |---|---|
-| `benchmark/` | The 15 tasks: `paper<i>/task_spec.md`, the original paper (`paper.pdf`, its text `paper.md`, figures `images/`) and `index.csv` (domain, venue, lab, link to the original paper, the follow-up direction). The code and data a task uses are downloaded from their original sources by `prepare_tasks.py` in the GitHub repository. |
-| `outcomes/` | The follow-up papers the agents wrote: `<agent>/paper<i>.pdf` is the `proposal/report.pdf` of that submission, the PDF the judge read. `index.csv` lists every submission; four GLM-5.3 runs produced no PDF. |
-| `file_systems/` | For every submission, the files the judge read: `proposal/` plus the rest of the agent's working directory (as `workdir_outside_proposal/`). Python/conda environments, caches, agent configuration files and the final transcript `ai_scientist_trajectory.json` were not shown to the judge and are not included; for Astra-6 and Opus-5.5 the view does contain the runner's streamed transcript `ai_scientist_trajectory.jsonl`. Each submission is an uncompressed tar split into parts, with `manifest.json` listing every file's path, size and SHA-256. For nine runs, `supplement.tar.part-*` and `supplement_manifest.json` add files of the run's working directory that the copy the judge read lacked, recovered from the original run folders (the judge did not see them): Opus-5 P1, P2, P9, P11 and P13, whose archived copies kept only `proposal/` and dropped checkpoints and files over 100 MB (50.7 GiB recovered), and a few files whose names differ only in case for Astra-6 P2 and P13 and Opus-5.5 P2 and P12. Extract `view.tar` and `supplement.tar` into the same folder. |
-| `trajectories/` | Each run's `ai_scientist_trajectory.json` (`<agent>/paper<i>.json`): run metadata (model, effort, attempts, run time) and every recorded agent event. DeepSeek-V4-Pro's harness kept its transcript in its own session logs, so its files hold only a few marker events. `<agent>/paper<i>.harness_logs.tar` hold each harness's own logs: DeepSeek-V4-Pro's session logs (`.dsh/`, its full conversation), GLM-5.3's OpenHands event log (`.oh_conversations/`) and Fable-5's runner logs (`_runlogs/`); `harness_logs.csv` lists them. `<agent>/paper<i>.runner_logs.tar` hold the console logs of the runner that drove the run (a one-line summary of each agent step, attempts, completion checks and final status; PBS job output for the ABCI runs), where they were kept; `runner_logs.csv` lists them. `index.csv` summarizes each run. |
+| `benchmark/` | The 15 tasks: `paper<i>/task_spec.md`, the original paper (`paper.pdf`, its text `paper.md`, figures `images/`) and `index.csv`. A task's code and data are downloaded by `prepare_tasks.py` in the GitHub repository. |
+| `outcomes/` | The papers the agents wrote, `<agent>/paper<i>.pdf` (the `proposal/report.pdf` the judge read): 131 PDFs, since four GLM-5.3 runs produced none. |
+| `trajectories/` | Each run's `<agent>/paper<i>.json` (run metadata and every agent event), plus the harnesses' own logs (`*.harness_logs.tar`; DeepSeek-V4-Pro's full conversation is here) and the runners' console logs (`*.runner_logs.tar`). |
+| `file_systems/` | Each submission's files as the judge saw them: `proposal/` and the rest of the working directory (`workdir_outside_proposal/`), without environments, caches or the final transcript. `view.tar.part-*` with a SHA-256 `manifest.json`; nine runs add a `supplement.tar` of files the judge's copy lacked. |
+
+Agents (`<agent>`): `opus-4.8`, `opus-5`, `opus-5.5`, `fable-5`, `sol-5.6`, `astra-6`, `deepseek-v4-pro`, `kimi-k3`, `glm-5.3`.
+
+**Dataset Structure**
+
+An example of a `benchmark` datum is as follows:
+
+```
+paper: (str) - The task id, P1 to P15.
+group: (str) - A: published 2024 or earlier; B: submitted 2026.
+title: (str) - The original paper's title.
+domain, venue, lab: (str) - Its field, venue and the laboratory of its authors.
+citations: (int) - Citations as of September 14, 2026.
+original_paper: (str) - A link to the original paper.
+follow_up_direction: (str) - The research direction the paper's author proposed.
+task_spec, paper_pdf, paper_md: (str) - Paths to the task specification and the original paper in this dataset.
+```
+
+`outcomes/index.csv` and `trajectories/index.csv` list one row per submission (agent, paper, file, and run metadata).
 
-Agents (`<agent>`): `opus-4.8`, `opus-5`, `opus-5.5`, `fable-5`, `sol-5.6`, `astra-6`, `deepseek-v4-pro`, `kimi-k3`,
-`glm-5.3`.
+**Evaluation**
 
-### Unpacking a file system
+Run an agent and judge its submission with the [GitHub repository](https://github.com/prometheus-eval/into-the-unknown):
 
 ```bash
-huggingface-cli download prometheus-eval/shoulders-of-giants --repo-type dataset \
-    --include "file_systems/astra-6/paper3/*" --local-dir .
-cd file_systems/astra-6/paper3
-cat view.tar.part-* > view.tar && tar -xf view.tar      # proposal/ and workdir_outside_proposal/
+bash src/solver/run.sh <agent> <paper_id>
+python src/grader/run_codex_judge.py prepare --agents <agent>     # then rescope, launch
 ```
 
-`manifest.json` gives each file's SHA-256 (as recorded by the judge when it graded the submission) and each part's
-SHA-256, so a download can be checked file by file.
+To unpack one submission's files:
 
-## Notes
+```bash
+huggingface-cli download prometheus-eval/into-the-unknown --repo-type dataset \
+    --include "file_systems/astra-6/paper3/*" --local-dir .
+cd file_systems/astra-6/paper3 && cat view.tar.part-* > view.tar && tar -xf view.tar
+```
+
+A few notes specific to this dataset:
 
-- `outcomes/fable-5/paper8.pdf`: the agent put a real person's name, affiliation and e-mail address on its title page;
-  they are blacked out here. All other PDFs are byte-identical to the submissions.
+- `outcomes/fable-5/paper8.pdf` has a real person's name, affiliation and e-mail blacked out on its title page; every other PDF is byte-identical to the submission.
 - Files written on the compute cluster can contain absolute paths of the cluster's file system.
-- `file_systems/opus-5.5/paper12`: two third-party R help pages (`proposal/tools/Rlib/fields/help/qsreg.html`,
-  `proposal/tools/Rlib/spam/help/spam.html`) have names that differ only in case from other help pages, so the
-  judge's copy on a case-insensitive file system held another page's content under these names. The archive has
-  the original files; `manifest.json` lists both under `checked_against_judge_record.sha256_mismatch`, and the
-  other pages are in `supplement.tar`.
-
-## License
-
-Task specifications, rubrics and this dataset's own documentation are released under the Apache-2.0 license of the
-GitHub repository. The original papers in `benchmark/` remain under their authors' and publishers' terms and are
-included for research use. Agent outputs (`outcomes/`, `file_systems/`) may contain third-party code and data the
-agents downloaded, which keep their own licenses.
+- In `file_systems/opus-5.5/paper12`, two R help pages (`qsreg.html`, `spam.html`) differ only in case from other pages; the archive has the originals, the others are in `supplement.tar`, and `manifest.json` lists both under `checked_against_judge_record.sha256_mismatch`.
+
+**License**
+
+Task specifications, rubrics and documentation are released under the Apache-2.0 license of the GitHub repository. The original papers in `benchmark/` remain under their authors' and publishers' terms and are included for research use; agent outputs may contain third-party code and data that keep their own licenses.