What is verified environment?

A verified environment is one that ran its own declared test command at build time, so it is known to work before an agent is placed inside it.

Verification is a build-time gate, not a runtime check. You declare a verify command with the snapshot, usually the same command your CI runs, and the snapshot is stored only if it exits zero. A failed verification costs nothing.

Without it, a broken environment reaches an episode, the agent fails inside it, and the result is recorded as the agent failing the task. At one episode you would notice. At a thousand you do not.

This is one of the terms in the Promigence glossary.

Run your own workload on it, free

Send a repo and the command you run against it, whatever that is: an eval suite, an RL rollout, a CI job, a queue of coding tasks. We build the environment once, run it a thousand times, and send back the timings, the failures and an exact price. Free, once, on your real workload.

1,000 runs of your own command, on your own repo
What each one cost in wall clock, and anything that failed
Whether a failure was your code or the environment
An exact price for your real volume

Not ready to hand over a repo? Read the quickstart or check the numbers first.