RL ENVIRONMENTS

Give agents somewhere to learn.

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.

Illustrative attemptStatic replay · no cloud sandbox executed
Start stateClean reset

Reset world to digest-pinned repository state

Environment boots cleanly from a pinned container image and task manifest. Failing test reproduces a duplicate-charge bug on retry.

Pinned manifestenv://billing-retry@sha256:4f8a…c21 · split: practice · network: isolated

01 / Task, world, verifier, outcome

A task should be more than a prompt.

An agent needs somewhere to act, a clear end condition, and a verifier that can distinguish a completed job from a convincing explanation.

Task
What the agent is asked to do, written as a versioned problem statement without leaking hidden test bodies or reference patches.
World
The initial state, files, and tools the task runs in—reconstructed so every candidate sees the same starting conditions. Task families include SRE incident recovery and multi-tool co-work, built as tool simulations rather than native applications.
Verifier
A versioned check of the final state of the world, not the agent's summary of what it tried.
Outcome
The verifier verdict and run receipt kept against the exact environment version it ran on.

02 / Reproducible starts

Reset. Attempt. Check.

Reproducible task definitions let teams compare different agents or versions on equivalent starting conditions. Versioning protects the meaning of the result.

Clean starting state

Each environment pins its image digest, task definition, parameters, and tool surface so every rollout begins from the same world.

Content-addressed versions

Change the task list, image digest, verifier release, reward contract, split, or rights snapshot and the registry assigns a new content address.

Equivalent comparisons

Every episode and export records its exact environment version so comparisons across candidates stay anchored to the same bar.

03 / Robust grading

A verifier should reject the wrong fix.

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.

Wrong-fix probes
Before a verifier grades sealed tasks, it is tested against plausible wrong patches and bypass attempts so false-accept rates are measured. A task instance is admitted only after its reference solution passes that instance's own signed verifier; a clean process exit is not accepted as proof.
State over self-report
Checks inspect actual repository, file, or system state rather than grading an agent's persuasive explanation.
Human adjudication
When a task requires specialist judgment, outcomes stay provisional until a qualified reviewer records the decision.

04 / Portable manifests

Carry the environment with the evidence.

Versioned task manifests, pinned artifacts, defined reviewer decisions, and Harbor package exports make it easier to inspect what was evaluated.

CapabilityCurrent delivery scopeTechnical contract
Versioned registryAvailable by signed scopeEach 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 exportAvailable by signed scopeDelivered 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 JSONLScoped per engagementExport adapters follow the same SHA-256 manifest and sealed-split exclusion rules; compatibility with your harness is verified in scope before delivery.
Isolated sandbox hostingScoped per engagementExecution infrastructure and any dedicated sandbox fleet are confirmed and validated during scoping rather than assumed as an active hosted pool.

05 / Scoped execution

Scope the execution you need.

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.

Practice split
Environments for trying an agent and inspecting what the verifier reports before committing to larger runs.
Train split
Tasks set aside for training by the customer or an approved provider under explicit rights.
Sealed split
Held-out tasks used only to evaluate. A sealed task is never exported in any format, and neither are its trajectories, even if it is unsealed later. Every export lists how many sealed items it left out.
Public catalogue

No catalogue entries to show right now.

Availability and hosting are confirmed during scoping.

Scope an environment

Scope an environment

Bring the task and the check that decides it.

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.