Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Artifacts and outputs

The versioned files a superagent's team produces and builds on, and the outputs it produces for you.

A superagent's team produces two kinds of results: artifacts, the working files team members build on, and outputs, the finished results produced for you.

Artifacts
Outputs

What they are

Versioned files, such as datasets, models, scored results or drafts

Results for you to read, such as documents, charts and reports

Who uses them

Other team members, and you

You

Where to find them

A team member's Artifacts tab on the Map

The Outputs tab

Artifacts

An artifact is a file the team publishes so that others can build on it. A worker might publish a cleaned dataset, which another worker uses to train a model, which a third uses to produce a backtest.

Each artifact has a name, a type (a free-form label such as "dataset" or "model"), a description and a version history.

Versions

Every time an artifact is updated, a new version is added: v1, v2 and so on, with the newest marked (latest). Earlier versions are kept, so the superagent can compare versions to check what changed, and you can download any of them.

A version can be a single file or a folder of files. It's either produced by a team member or uploaded by you.

Lineage

Artifacts record where they came from. When one artifact is built from another, it's marked as derived from it, either because the team member said so or because Zerve worked it out. That gives you a lineage you can trace, from a final result back to the data it started from.

Because of this, an artifact can't be deleted while other artifacts are derived from it.

Working with artifacts

To
Do this

See who produced what

On the Map, turn on the Artifacts layer to see how many artifacts each team member has produced

See a team member's artifacts

Select the team member on the Map and open its Artifacts tab. Its Input tab shows the artifacts it's working from.

Upload your own

Upload a file as an artifact, for example a dataset or a reference document you want the team to use

Download

Download any version

Delete

Delete an artifact or a single version, as long as nothing is derived from it

Artifacts in batches

In Tournaments and other judged batches, entrants publish their work as artifacts, and the judges compare the published artifacts.

Outputs

Outputs are what the team produces for you to read: documents, charts, reports and other files. The Outputs tab on a superagent's page lists them all, with a count, for example Outputs (12). You can also see the outputs of a single team member in its Output tab on the Map.

Checking results

Superagents check work before presenting it, and they can require results in a particular form, such as a number within a set range. See How superagents approach work.

Last updated

Was this helpful?