---
id: assets.weights
title: Weights
summary: Understand the current Weights asset surface and the absence of a public model-weight lifecycle.
kind: reference
product_area: assets
status: stable
updated: 2026-09-07
canonical: /docs/assets/weights
---

# Weights

## Definition

Weights is a visible project-level Asset category for model-weight artifacts. The current page presents an empty state and does not expose upload, registration, versioning, activation, deployment, or evaluation controls.

Model provider, model name, configuration, and execution receipts can appear in Harness Version or Run evidence. Those fields are not a Weights asset lifecycle.

> Current capability boundary
>
> Do not claim that model weights can be imported, fine-tuned, deployed, or compared from Assets until those actions and their durable identities are exposed by the product.

## Fields, states, or lifecycle rules

The current page defines no public weight fields, artifact states, or lifecycle actions. Model and provider facts in candidate or Run evidence remain owned by those records.

## What to record instead

When candidate behavior depends on a model, preserve the exact Harness Version and the model or provider configuration recorded by its source, runtime facts, Run Metadata, or evaluation receipt. Do not create a fictional Weights asset to make an experiment look versioned. Candidate code and dependency changes belong in Harness publication; evaluation evidence belongs to the Run and immutable Benchmark Version.

Run telemetry can report tokens, cost, or latency when captured. Those values describe execution and do not establish that a model checkpoint has been registered in Weights. Likewise, an Improvement Session candidate remains a saved Harness Version even when its behavior depends on model selection.

The empty state does not provide a weight artifact ID, supported format, upload action, version, Harness attachment, fine-tuning job, or deployment control. Use active Harness, Run, and provider-evidence surfaces for currently inspectable candidate identity.

{% related-card-grid title="Current related boundaries" %}
- [Manage Harnesses](/docs/assets/harnesses)
- [Configure Run Metadata](/docs/benchmark-evaluations/run-metadata)
- [Inspect evaluation results](/docs/benchmark-evaluations/inspect-results)
{% /related-card-grid %}

## Related task pages

{% related-card-grid title="Related task pages" %}
- [Manage Harnesses](/docs/assets/harnesses)
- [Run a benchmark evaluation](/docs/benchmark-evaluations/run-evaluation)
{% /related-card-grid %}

## Source confidence

Code-backed: the Assets layout exposes the Weights tab and the current route renders “No Weights yet.” No additional public behavior is claimed.