> For the complete documentation index, see [llms.txt](https://docs.hatchr.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hatchr.fun/security/administrative-controls.md).

# Administrative Controls

Hatchr is not presented as fully ownerless. The deployed system contains explicit administrative roles.

## Factory owner

The factory owner can update:

* launch fee;
* minimum required ETH;
* creator share of collected LP fees;
* launch tick; and
* platform fee wallet.

The factory rejects any nonzero creator token allocation.

## Initializer owner

The `TokenInitializer` owner controls which factories may initialize token clones.

## Locker owner

The `LPLocker` owner controls which factories may register positions and locked dust.

## What these roles cannot do

The current contracts do not provide an administrator with a function to:

* mint additional supply for an existing token;
* seize holder balances;
* blacklist transfers;
* add a token transfer tax;
* pause an existing token;
* upgrade an existing minimal clone; or
* withdraw a registered LP position NFT from the locker.

{% hint style="info" %}
Parameter changes are observable on-chain through transactions and emitted events. Integrators should monitor owner and configuration changes.
{% endhint %}


---

# 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.hatchr.fun/security/administrative-controls.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.