agentic-ptb/sol-max-opusnode-data

1---2tags: [agentic-ptb, sol-max-opusnode, training-data]3---4 5# sol-max-opusnode-data6 7Training data built by the AgentPTB arm for cell **`sol-max-opusnode`** — Codex / gpt-5.6-sol @ effort `max`.8 9This is the corpus the arm *itself* assembled during its 100-hour run: what it downloaded,10filtered, rewrote and mixed. It is the input side of the checkpoints published as11`agentic-ptb/sol-max-opusnode.h*`, and the companion to the run record in `agentic-ptb/sol-max-opusnode-record`.12 13| field | value |14|---|---|15| plot cell | `sol-max-opusnode` |16| driver | Codex / gpt-5.6-sol |17| reasoning effort | `max` |18| total size | 8.28 GB |19| path in run | `/mnt/pvc/users/simon/agentptb/runs/sol-max-opusnode/workspace/data` |20 21## Largest components22 23| directory | size |24|---|---|25| `processed` | 8.28 GB |26| `raw` | 0.0 GB |27 28## A note on apparent secrets29 30Automated scanning flags credential-shaped strings (`AKIA…`, `sk-…`, `AIza…`) in these31corpora. They were checked: they are **synthetic fixtures inside the training tasks32themselves** — secret-scanning and config-hygiene exercises whose task text embeds fake keys33(`"secret_type": "api_key"`, `"matched_pattern": …`). No credential belonging to this project34appears in the data.35 36## Related37 38- `agentic-ptb/sol-max-opusnode-record` — driver trajectory, harness, configs, evals for this cell39- `agentic-ptb/sol-max-opusnode.h*` — the checkpoints trained on this data40- `agentic-ptb/INDEX` — manifest joining every checkpoint back to the sweep figures41