> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/artifacts/what-are-artifacts.md).

# What Are Artifacts?

### Overview

Artifacts store supporting material for delivery work.

They preserve context that requirements, tasks, and tests can reference.

### Key Concepts

* **Artifact**: Transform entity that stores a file, link, or reference note
* **Scope**: location where the Artifact is created (Account or Project)
* **Source**: how the Artifact is created, such as upload or link
* **Traceability**: links between Artifacts and downstream work items

### How It’s Used

Use Artifacts to store and share:

* existing documentation, such as requirements documents, statements of work, and designs
* Spreadsheets and exports
* decisions, meeting outputs, and reference materials

Use links from requirements and tasks to keep evidence attached to scope.

### Benefits

* Less duplicated context across comments and messages
* Faster onboarding through stable reference material
* Stronger governance through traceable evidence and sources

### Setup Steps

1. Decide the scope for the Artifact.
   * Use **Account** scope for reusable references and standards.
   * Use **Project** scope for delivery-specific material.
2. Create the Artifact.
3. Link the Artifact from requirements, tasks, and tests that rely on it.

### Best Practices

* Use stable names that match the governance cadence.
* Prefer links to source items over copying long text.
* Archive outdated Artifacts when auditability matters.

### Summary

Artifacts provide the reference layer for delivery work and governance.

Related:

* [Creating Artifacts](/artifacts/creating-artifacts.md)
* [Quick Notes](/artifacts/quick-notes.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.transform.ai/artifacts/what-are-artifacts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.