Environments serve as a unified specification for a task: they encapsulate data, the scenario, how an agent interacts, and how outcomes are scored. The speaker argues the first thing to do with an environment is just evaluations, making environments the entry point for post-training, not only RL.
Treating environments as the central abstraction forces consistency between evaluation and training data, reduces duplicate scaffolding, and lowers the barrier to adding post-training for practitioners who already have evals.
Any team doing post-training should first encode tasks as environments that include interaction and scoring, then reuse those environments for evals, RL, and other training methods.
environments are a language for specifying what you want your model to do.
They are an encapsulation of the data you might have, the scenario you might want your agent to be in, the way it'll interact with that environment, as well as how to score what good looks like.
often this is the first thing you'll want to do with an environment is just evals.