STEP 01
WHAT GETS BUILT
Build the environment
The teams who run the work spec the environment. Reward, reset, state, action — written once by the people who use it.
→AI LABS · RL ENVIRONMENTS · BUILT BY THE PEOPLE WHO USE THEM
Environments built by the people who use them.
Reviewed once. Approved once. Available to every team that needs them.
CATALOG
22 approved
Environments your teams can pull and run today.
RUNS
48 deployed
Same environment. Different team. Same answer.
SIGNED
Approved once
Review records, version registry, and usage logs travel with it.
HOW IT WORKS
Three steps. One registry.
Build the environment. Review and approve. Share it across the teams that need it.
STEP 02
WHAT GETS APPROVED
Review and approve
Submissions pass a single review. Static checks, policy gates, and human signature. Nothing reaches a runner unapproved.
→STEP 03
WHAT GETS REUSED
Share across teams
Approved environments land in the catalog with their version, owner, and usage log attached. Every team pulls the same artifact.
WHAT COMES OUT
What your team leaves with.
Every approval leaves a record. Every run leaves a log. Every team works against the same artifact.
01
Environment specs
Reward, reset, state, and action — written down by the people who run the work.
↳ ARTIFACT
02
Approval records
Static checks, policy gates, and the reviewer signature that opened the door.
↳ ARTIFACT
03
Version registry
Every version of every approved environment, with owner, lineage, and the runs that depend on it.
↳ ARTIFACT
04
Usage logs
Which team ran it. Which run consumed it. What the result was.
↳ ARTIFACT
WHERE IT FITS
In the loop, this is where you test.
Test the run against the environment. Review what broke. Recruit the specialist. Remember the miss. Approve what's right.
01
Test
● YOU ARE HERE
02
Review
03
Recruit
04
Remember
05
Approve
READOUT · DECISION GRAPH
RELATED MODULES
Next to this in the Model OS.
TRAINING
Train against the same environment.
Every team starts from the approved spec. No drift between research and production.
See the page →AUTOPILOT
Run the workflow without the toil.
Schedule runs across approved environments. The catalog is the contract.
See the page →SYNTHETIC POPULATIONS
Populate the environment with people.
Pair an approved environment with a population that matches the workload.
See the page →RL ENVIRONMENTS
Built by the people who use them.
Bring the environment your team already runs. We'll review it once and make it available to every team that needs it.