> For the complete documentation index, see [llms.txt](https://docs.flxbl.io/flxbl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flxbl.io/flxbl/sfp/development/defining-a-domain.md).

# Defining a domain

A domain is defined by a release configuration. In order to define a domain, you need to create a new [release config ](/flxbl/sfp/development/defining-a-domain/release-config.md)yaml file in your repository

A simple release config can be defined as shown below

<pre class="language-yaml"><code class="lang-yaml">// Sample release config &#x3C;business_domain.yaml>
releaseName: <a data-footnote-ref href="#user-content-fn-1">&#x3C;business_domain>  </a> # --> The name of the domain
pool: <a data-footnote-ref href="#user-content-fn-2">&#x3C;sandbox/scratch org pools></a>
excludeAllPackageDependencies: true
includeOnlyArtifacts:   # --> Insert packages
  - <a data-footnote-ref href="#user-content-fn-3">&#x3C;pkg1></a>
releasedefinitionProperties:
  promotePackagesBeforeDeploymentToOrg: prod
</code></pre>

The resulting file could be stored in your repository and utilized by the commands such as build, release etc.

[^1]: Replae with domain

[^2]: Pools of orgs where the change should be validated

[^3]: Insert your packages here


---

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

```
GET https://docs.flxbl.io/flxbl/sfp/development/defining-a-domain.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.