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

# Foundation and operating company

Gimbal Foundation holds governance and the contracts; Gimbal Labs builds and runs the platform. Why the two are kept apart, and the path by which parameter control leaves the multisig for on-chain gov

Gimbal is held by two entities with deliberately different jobs, and the protocol would keep running if one of them disappeared.

## Why the split

* The contracts are immutable and hold nothing in custody. Putting them under a foundation keeps governance clear of the commercial interests of the builder.
* A front end faces users and needs licences in some places. That is the operating company's job, and keeping it separate limits the regulatory surface attached to the protocol.
* The code is open source. If the operating company closed, anyone could stand up their own relayer, indexer and front end, and the contracts would carry on unchanged.

## Responsibilities

|                     | Gimbal Foundation                                                                | Gimbal Labs (operating company)                              |
| ------------------- | -------------------------------------------------------------------------------- | ------------------------------------------------------------ |
| Holds               | The immutable contracts and protocol governance                                  | The platform, reference relayer, indexer and keeper software |
| Controls            | The parameter multisig behind the timelock, until a governance module takes over | Day-to-day operation of everything off chain                 |
| People and licences | None                                                                             | Employs the team; licensed wherever a licence is required    |

## Governance, today and next

**Today.** Parameter changes are made by the foundation's timelocked multisig. Each proposal is published together with its rationale.

**Next.** Control of parameters passes to a governance module. Four properties survive the handover: the timelock, the published rationale, no path to user funds, and nothing that can pause repayment.

## The token

$GIMBAL is deployed on Robinhood Chain at `0xe33ab021662e23f745be8e5b237babe8c7ad626c`. Its supply is fixed and governance has no way to mint more. [How parameters change](/transparency/parameter-changes.md) describes the change process in full.


---

# 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.usegimbal.app/compliance/entities.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.