Assets
Assets is the project-level pool for cases, worlds, project tools, harnesses, weights, Comparison Directions, and Review Screens. Assets are managed once at project scope and selected for use in a specific benchmark rather than being recreated inside every benchmark workspace.
Definition
The active tabs are Cases, Worlds, Project Tools, Harnesses, Weights, Comparison Directions, and Review Screens. Cases provide the canonical situations evaluated or reviewed. Harnesses provide executable candidate implementations with Draft and saved Versions. Comparison Directions guide comparative output variation, and Review Screens provide reusable expert-facing presentation templates. Worlds, Project Tools, and Weights are visible categories whose current pages expose empty states rather than creation or lifecycle controls.
Assets is distinct from Benchmark Datasets. The project pool answers what is available to the project. A benchmark dataset answers which cases and snapshot define one benchmark's evidence boundary.
Decision checkpoint
| Need | Asset or workspace | Boundary |
|---|---|---|
| Create or inspect a reusable situation | Assets → Cases | Case content follows Project Input Schema |
| Edit candidate code or prompt logic | Assets → Harnesses | A Draft must be saved as an exact version before evaluation |
| Select cases for a benchmark | Benchmark Datasets | Selection and snapshot are benchmark-scoped |
| Supply static documents or values to a case | Case materials | Static support is not a World |
| Inspect planned environment assets | Worlds | Current product exposes the category but no public lifecycle yet |
| Inspect planned callable project assets | Project Tools | Current product exposes the category but no public lifecycle yet |
| Inspect planned model-weight assets | Weights | Current product exposes the category but no public lifecycle yet |
| Guide comparative output variation | Comparison Directions | Direction guidance is separate from coverage structure and approval |
| Configure reusable expert-facing presentation | Review Screens | Presentation is separate from Case content and Contribution objectives |
Project reuse and benchmark selection
Project scope makes assets reusable across multiple benchmarks. That reuse also increases the impact of changes. Editing a case can affect any future benchmark snapshot that selects it. Saving a new Harness version does not silently change Runs that referenced an older version. Benchmark evidence should always identify the exact asset versions or snapshot involved.
Worlds, Project Tools, and Weights are visible product categories, but their current pages do not expose durable user actions. Do not infer persistence, activation, execution, or evaluation semantics from the navigation label alone. Their reference pages record this limitation so operators and agents do not invent a workflow.
Relationship to the five capabilities
Weave creates and curates cases and supporting materials. Trialground evaluates saved Harness versions. Coevolve can materialize or evaluate candidate Harness versions during Improvement Sessions. Coverage Engineering and Correctness Elicitation influence which cases and candidates are useful, but ownership remains with the appropriate Asset or governed project surface.
Worked example
Shared harness pool
A project contains two saved retrieval Harness versions and one draft experiment. Two benchmarks select different case snapshots but can evaluate either saved Harness version. The draft remains editable and cannot be mistaken for the candidate used by an existing Run. Compare can therefore attribute result movement to the saved candidate and benchmark evidence boundary.
Related workflows
Related reference pages
Source confidence
Code-backed: the active Assets layout and navigation establish the project-level pool and tab names. Cases, Harnesses, Comparison Directions, and Review Screens have active surfaces; the current Worlds, Project Tools, and Weights routes expose empty states only.