Clean starting state
Each environment pins its image digest, task definition, parameters, and tool surface so every rollout begins from the same world.
RL ENVIRONMENTS
A task they can attempt. A starting state you can reproduce. A result you can actually check. Build and evaluate agents on the work they need to get right.
AuraOne RL Environments are versioned, resettable task environments with state-checked verifiers, content-addressed artifacts, and Harbor package exports scoped for your agent harness.
Environment boots cleanly from a pinned container image and task manifest. Failing test reproduces a duplicate-charge bug on retry.
env://billing-retry@sha256:4f8a…c21 · split: practice · network: isolated01 / Task, world, verifier, outcome
An agent needs somewhere to act, a clear end condition, and a verifier that can distinguish a completed job from a convincing explanation.
02 / Reproducible starts
Reproducible task definitions let teams compare different agents or versions on equivalent starting conditions. Versioning protects the meaning of the result.
Each environment pins its image digest, task definition, parameters, and tool surface so every rollout begins from the same world.
Change the task list, image digest, verifier release, reward contract, split, or rights snapshot and the registry assigns a new content address.
Every episode and export records its exact environment version so comparisons across candidates stay anchored to the same bar.
03 / Robust grading
Known wrong answers, prompt variations, and adversarial cases help establish whether a check is robust. Tasks needing a person's judgment stay provisional until that decision is recorded.
04 / Portable manifests
Versioned task manifests, pinned artifacts, defined reviewer decisions, and Harbor package exports make it easier to inspect what was evaluated.
| Capability | Current delivery scope | Technical contract |
|---|---|---|
| Versioned registry | Available by signed scope | Each published version has one content address covering the image digest, the exact task list, task specs and parameters, the verifier release, the reward contract, the split, and the rights snapshot. |
| Harbor package export | Available by signed scope | Delivered as an AuraOne bundle or native Harbor task layout. Every file is listed with its size and SHA-256, and import rejects any changed, missing, or extra file before writing. |
| OpenEnv, verifiers & reward JSONL | Scoped per engagement | Export adapters follow the same SHA-256 manifest and sealed-split exclusion rules; compatibility with your harness is verified in scope before delivery. |
| Isolated sandbox hosting | Scoped per engagement | Execution infrastructure and any dedicated sandbox fleet are confirmed and validated during scoping rather than assumed as an active hosted pool. |
05 / Scoped execution
Environment formats and hosting models are selected and validated for the engagement. The commercial product is RL Environments; availability of a particular sandbox fleet or extra export adapter is an implementation detail to confirm when defining scope.
Availability and hosting are confirmed during scoping.
06 / Connected workflow
The same task family can help reveal a weakness, shape a learning program, and test the next model candidate without leaking sealed evaluation material into training.
Scope an environment
We scope each environment with your team: the task, the world, the verifier, and the export package. Hosting and extra adapter requirements are confirmed during scoping.
Guides