# Turn task expectations into a reviewable definition

Canonical: https://savrn.com/cloud/environments

SAVRN Cloud · Coming soon. Public documentation and a browser simulation are available; connected services are not yet available.

An environment describes the task a model is asked to perform and how its behavior will be assessed. SAVRN Cloud’s preview makes the rubric, threshold and version visible so teams can inspect those assumptions. It uses local demonstration records. Connected evaluation and training environments are Coming soon.


## Describe the behavior that matters

A research task may require a cited answer, a structured extraction or a bounded tool action. Its environment should explain the expected input, allowed behavior, termination condition and scoring method. This definition is distinct from the cases used to test it. A clear boundary helps a researcher decide whether the task actually represents the intended use.

## Explore a versioned rubric

Open a preview environment and inspect its configuration. The local controls let you change the rubric, score threshold and displayed timeout, creating a new version while earlier results retain their recorded context. Export the configuration to inspect the sample definition. These actions demonstrate revision tracking; they do not run an external verifier or training process.

## Review scoring assumptions explicitly

Different rubrics can reward different behavior even when the underlying model and examples remain unchanged. Consider whether a high score could conceal missing evidence, formatting shortcuts or unsupported conclusions. Planned connected environments need tests for the scoring procedure itself, including representative failures. A score is only as useful as the task and measurement behind it.

## Separate shared methods from private cases

A team may want to reuse a task definition while restricting the dataset or supporting materials. The intended design needs clear ownership, version references and access rules for each component. Public examples should disclose only material that can be shared. Private registry behavior and cross-project permissions must be implemented and qualified before an environment becomes a connected institutional resource.

## What you can explore today

Inspect and revise sample rubrics, preserve local version context and export demonstration configurations.

## Before this service launches

Connected environments require tested task execution, validated scoring, artifact versioning and enforceable registry access.

## The customer outcome

The intended outcome is a task definition that researchers and reviewers can inspect, revise and reference when interpreting an evaluation or training experiment.

## Related documentation

- [Environments overview](https://savrn.com/cloud/docs/environments-overview)
- [Build and test an environment](https://savrn.com/cloud/docs/environments-build-test)
- [Private environment registry](https://savrn.com/cloud/docs/environments-private-registry)
- [Explore environments](https://savrn.com/cloud/console/#/environments): Inspect a sample task definition and its rubric.