> ## Documentation Index
> Fetch the complete documentation index at: https://www.scrums.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Deployments

> How a catalog item becomes a running deployment: cart, checkout, claim, and the deployment lifecycle.

## What a deployment is

A **deployment** is one provisioned service line — a single quoted or sold unit of delivery, tracked end to end.

Every deployment carries a permanent identifier:

```
DEP-10000001
```

The code is `DEP-` followed by 8 digits. It is minted once and never changes, even when the deployment is paused, superseded, or completed.

## Cart

You add catalog items to a cart from any `/products/{slug}` page. A cart may mix primitives — engineers, an agent, and infrastructure can sit in one order.

Nothing is provisioned while items are in the cart. No deployment code exists yet.

## Checkout

Checkout converts the cart into an order. At this point Scrums.com:

1. Records the order against your organisation.
2. Mints a `DEP-` code for each service line in the order.
3. Starts matching and provisioning for each line.

Each line becomes its own deployment. One order with three service lines produces three deployment codes.

## Claim

Claiming links a deployment to the person or team who will run it.

An unclaimed deployment is provisioned but has no owner in your workspace. Claim it to attach it to a workspace, grant access, and start delivery.

<Note>
  Claim is an ownership action, not a payment action. Checkout creates the deployment. Claim decides who operates it.
</Note>

## Deployment lifecycle

| Status          | Meaning                                                        |
| --------------- | -------------------------------------------------------------- |
| `pending_match` | Provisioned and awaiting a match — talent, agent, or resource. |
| `active`        | Running and delivering.                                        |
| `paused`        | Temporarily stopped. The code and history are retained.        |
| `completed`     | Delivered and closed normally.                                 |
| `cancelled`     | Stopped before completion.                                     |
| `superseded`    | Replaced by a newer deployment. The old code stays for audit.  |

A deployment never loses its code. Status changes; identity does not.

## Where to look next

* [Catalog Overview](/docs/products/catalog) — how items are organised
* [Administration](/docs/administration/billing) — billing against deployments