> For the complete documentation index, see [llms.txt](https://docs.gysr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gysr.io/concepts/factory.md).

# Factory

## [🏭](https://emojipedia.org/factory/)

In order to extend the principles of modularity and extensibility to the Pool factory, we introduce the concept of a module factory. This sub-factory is responsible for the construction of its respective module and is managed by the primary Pool factory. Each module factory must be whitelisted by the Pool factory controller before it can be used.

The Pool factory `create` method can be called by any user to configure and deploy a new Pool. The desired module types are specified by passing the corresponding factory addresses. Additionally, the constructor data for each sub-factory is passed through a pair of flexible bytes parameters. This primary factory method calls each module factory and assembles the overall Pool contract

*You can find all deployed factory addresses listed here*

{% content-ref url="/pages/IYSBl5Jk8akqyBc3f9fv" %}
[Deployment addresses](/developers/addresses.md)
{% endcontent-ref %}


---

# 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://docs.gysr.io/concepts/factory.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.