> For the complete documentation index, see [llms.txt](https://archivedocs.stackstate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://archivedocs.stackstate.com/5.1/develop/developer-guides/stackpack/stackstate-common-layer.md).

# StackState Common Layer

A Layer is a specific term in the StackState where all the Components from different integrations lie within. It's used for the horizontal ordering of the topology. Since StackState supports multiple integrations, there are some common layers defined in the product. Layers are ordered in terms of proximity to the end-user. Merging preference is given to the component in the layer which is closer to the end-user. Below is the list of common layers used in the StackState and their identifiers that can be referenced in a StackPack.

| Layer Name                 | Identifier                                            |
| -------------------------- | ----------------------------------------------------- |
| Blueprints                 | urn:stackpack:common:layer:blueprints                 |
| Users                      | urn:stackpack:common:layer:users                      |
| Business Processes         | urn:stackpack:common:layer:business-processes         |
| Applications               | urn:stackpack:common:layer:applications               |
| Application Load Balancers | urn:stackpack:common:layer:application-load-balancers |
| Uncategorized              | urn:stackpack:common:layer:uncategorized              |
| Services                   | urn:stackpack:common:layer:services                   |
| Serverless                 | urn:stackpack:common:layer:serverless                 |
| Containers                 | urn:stackpack:common:layer:containers                 |
| Processes                  | urn:stackpack:common:layer:processes                  |
| Messaging                  | urn:stackpack:common:layer:messaging                  |
| Databases                  | urn:stackpack:common:layer:databases                  |
| Machines                   | urn:stackpack:common:layer:machines                   |
| Storage                    | urn:stackpack:common:layer:storage                    |
| Networking                 | urn:stackpack:common:layer:networking                 |
| Hardware                   | urn:stackpack:common:layer:hardware                   |
| Locations                  | urn:stackpack:common:layer:locations                  |

The above layer list will be shown on the StackState Integration View from top to bottom. It means `Blueprints` layer will be on top and `Locations` layer will be at the bottom.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://archivedocs.stackstate.com/5.1/develop/developer-guides/stackpack/stackstate-common-layer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.