This branch was auto-updated!

website/docs/reference/artifacts/dbt-artifacts.md

@@ -19,15 +19,19 @@ They could also be used to:
 
 dbt has produced artifacts since the release of dbt-docs in v0.11.0. Starting in dbt v0.19.0, we are committing to a stable and sustainable way of versioning, documenting, and validating dbt artifacts.
 
-## When are artifacts produced?
+### When are artifacts produced? <Lifecycle status="team,enterprise"/>
 
 Most dbt commands (and corresponding RPC methods) produce artifacts:
-- [semantic manifest](/docs/dbt-cloud-apis/sl-manifest): Lives in the `/target` directory of your dbt project and stores various artifacts (such as compiled models and tests) generated during the execution of your project.
+- [semantic manifest](/docs/dbt-cloud-apis/sl-manifest): produced whenever your dbt project is parsed
 - [manifest](/reference/artifacts/manifest-json): produced by commands that read and understand your project
 - [run results](/reference/artifacts/run-results-json): produced by commands that run, compile, or catalog nodes in your DAG
 - [catalog](catalog-json): produced by `docs generate`
 - [sources](/reference/artifacts/sources-json): produced by `source freshness`
 
+## Where are artifacts produced?
+
+By default, artifacts are written to the `/target` directory of your dbt project. You can configure the location using the [`target-path`](/reference/project-configs/target-path#configuration).
+
 ## Common metadata
 
 All artifacts produced by dbt include a `metadata` dictionary with these properties: