---
id: assets.worlds
title: Worlds
summary: Understand the current Worlds asset surface without inferring an environment lifecycle that the product does not expose.
kind: reference
product_area: assets
status: stable
updated: 2026-09-07
canonical: /docs/assets/worlds
---

# Worlds

## Definition

Worlds is a visible project-level Asset category for executable or queryable environments. The current Worlds page presents an empty state and does not expose creation, configuration, versioning, activation, or lifecycle controls.

The Harness execution contract can carry an optional supported World instance reference, but that runtime boundary does not establish a user-facing Worlds management workflow.

> World versus case material
>
> Static files, documents, images, and values supplied with a case are case materials. Do not call them Worlds. A World requires an observable executable-environment identity and lifecycle, which the current Assets page does not yet expose.

## Fields, states, or lifecycle rules

The current page defines no public World fields or states. The optional runtime reference is the only verified adjacent contract and must not be expanded into a management lifecycle.

## What the runtime reference does establish

A saved Harness can receive an optional supported `world_instance_ref` with its request. That establishes a boundary between executable environment context and static `case_material_refs`. It does not reveal who creates the instance, how long it lives, which benchmark owns it, whether state resets between attempts, or how a user chooses one.

Treat the reference as optional runtime input. It does not promise deterministic reset, persistence, query APIs, tool availability, or replay. If a Run depends on a World reference, preserve the exact Harness and Run evidence that Teammately exposes and state any known environment limitation separately.

## What to use today

Use Project Input Schema and Case materials for static evidence. Use Harness source for supported candidate orchestration. Do not upload a directory or service endpoint to the Worlds empty state, invent a World ID, or describe a Case fixture as a managed environment.

The empty state does not provide a World ID, configuration, version, instance-creation action, reset control, Harness attachment, telemetry view, or archive action.

{% related-card-grid title="Current related boundaries" %}
- [Manage Harnesses](/docs/assets/harnesses)
- [Configure Project Input Schema](/docs/project-settings/input-schema)
- [Understand Dataset Snapshots](/docs/benchmark-datasets/snapshots)
{% /related-card-grid %}

## Related task pages

{% related-card-grid title="Related task pages" %}
- [Manage Harnesses](/docs/assets/harnesses)
- [Configure Project Input Schema](/docs/project-settings/input-schema)
{% /related-card-grid %}

## Source confidence

Code-backed: the Assets layout exposes the Worlds tab and its current route renders “No Worlds yet.” Runtime types support optional World references but do not justify additional public management claims.