# Environments overview

Canonical: https://savrn.com/cloud/docs/environments-overview

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

An evaluation environment connects a taskset, execution harness and scoring method so a result can be interpreted later. SAVRN Cloud's sample environment records let you inspect these relationships and see why reproducibility needs more than saving the original prompt.

**SAVRN Cloud · Coming soon · Public preview · Browser-local simulation · No live compute or payments**

## Open the local registry

Use [Environments](https://savrn.com/cloud/console/#/environments) to inspect a demonstration environment. **Configure** edits its rubric, pass threshold and timeout, incrementing its version. **Run** starts the evaluation path. Compare its task description, data and scoring approach. Follow related records in [Datasets](https://savrn.com/cloud/console/#/datasets) and [Evaluations](https://savrn.com/cloud/console/#/evaluations) to understand how an experiment becomes reproducible.

An environment is more than a prompt. It combines task inputs, an execution harness, permitted tools, a scoring method and runtime configuration. The local records illustrate those relationships, but no external package is installed or executed.

## Choose a small example

A useful synthetic environment asks a model to extract three fields from fictional research notes. Its taskset defines the notes and expected values. Its rubric describes accepted answers and failure cases. Its runtime identifies the tools needed to evaluate them.

Keep the example small enough for a reviewer to inspect every case. A large dataset does not compensate for unclear scoring.

## Before connected services launch

Version each component independently and freeze the combination used by a run. Record ownership, rights, dependencies, tool permissions, budgets and output schemas. Ensure the same environment can be evaluated before it is used for training. Review verifier limitations and opportunities for reward exploitation. A public registry entry needs explicit publication permission; private project materials must not become shared content by default. See [build and test](https://savrn.com/cloud/docs/environments-build-test) for a concrete proposed manifest.