> ## Documentation Index
> Fetch the complete documentation index at: https://aidocs.ethanbragdon.icu/llms.txt
> Use this file to discover all available pages before exploring further.

# Artifacts

> Understand Starfire AI build artifacts, packaging, metadata, checksums, ownership, downloads, and retention.

# Artifacts

Artifacts are durable outputs produced by Starfire workflows, especially FORGE builds. They separate the **result of a run** from the transient model conversation or worker that created it.

## Examples of artifacts

Depending on the workflow, an artifact can represent:

* a downloadable project archive
* generated source files
* a report
* build output
* packaged documentation
* other durable workflow output supported by the platform

## Artifact metadata

An artifact can carry metadata such as:

```text theme={null}
Artifact ID
Name
Owning user / organization / project
Source run or build
Created time
Size
File count
Checksum
Retention / expiration
Status
```

Metadata makes the output auditable and manageable without requiring an administrator to browse private file contents.

## Checksums

A checksum can help verify that a downloaded artifact matches the packaged output Starfire produced. A checksum confirms byte integrity; it does not guarantee that the software inside is correct or safe.

## Ownership

Artifacts should inherit a clear ownership context from the run, build, project, user, or organization that produced them.

Ownership affects who can download, delete, retain, or use the artifact.

## Retention

Artifact retention can depend on plan, organization policy, artifact type, or administrator configuration. Some artifacts can expire automatically to control storage use.

Before relying on Starfire as the only copy of an important production artifact, confirm the applicable retention behavior.

## Failed and orphaned artifacts

Operational failures can leave incomplete uploads or storage objects that are no longer attached to a valid artifact record. Control Center can expose metadata for failed uploads, expiring artifacts, storage consumption, and orphan cleanup.

<Warning>
  Administrator access to artifact operations should not imply unrestricted browsing of private user content. Operational metadata and content access are separate permission concerns.
</Warning>

## Developer access

The Developer Platform is designed to expose artifact operations programmatically as the public API surface is finalized.

<Card title="Build, Files & Artifacts API" icon="code" href="/developers/build-files-artifacts">
  Review the developer-facing model for long-running builds and artifact retrieval.
</Card>