> The first explanation is that they're benign fossils: agent logs from training sandboxes or third-party tools, swept into post-training unscrubbed. One clue fits. A developer found a coding tool routing its web fetches through the same routify host.
Case closed. Everything that passes the rollout ends up in the training data, probably because they don't monitor their rollouts the same way US labs have started to, as they're compute constrained.
Case closed. Everything that passes the rollout ends up in the training data, probably because they don't monitor their rollouts the same way US labs have started to, as they're compute constrained.