> ## 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.

# Catalog Overview

> How the Scrums.com catalog is organised: four primitive registers, flat item URLs, and how Platform relates to them.

## What the catalog is

The catalog is the register of everything you can buy or deploy from Scrums.com. Every item belongs to exactly one **primitive**.

Four primitives are catalog registers:

| Primitive    | What it registers                                                                 |
| ------------ | --------------------------------------------------------------------------------- |
| **Agents**   | AI agents that carry out work inside your delivery lifecycle.                     |
| **Delivery** | Engagement models and delivery services — sprints, audits, workshops, managed QA. |
| **Talent**   | Vetted engineers and specialists, as individuals, teams, or executive network.    |
| **Infra**    | Infrastructure, tooling, and services your delivery runs on.                      |

## Platform is not in the catalog

**Platform is a primitive, but it is not a register.** It holds no catalog items and has no catalog URL.

Platform is the bundled subscription that contains the four registers. You subscribe to Platform. You deploy items from the registers.

## Item URLs are flat

Every catalog item lives at one flat address:

```
/products/{slug}
```

The primitive is an attribute of the item, not a path segment. An item does not change its URL if its primitive is re-tagged.

<Note>
  Documentation is different. Docs nest under the primitive — `/docs/products/talent/…` — because a primitive holds several shapes and nesting shows that relation. The flat rule applies to catalog item URLs only.
</Note>

## Depth is uneven, and that is correct

Registers are not balanced. Infra holds hundreds of entries. Agents holds a handful.

Documentation does not mirror the register. These pages explain how a primitive works. They do not list its items. Browse the catalog itself for items.

## Next

* [Products & Engagement Models](/docs/products/overview) — how the primitives fit together
* [Deployments](/docs/products/deployments) — how an item becomes a running deployment