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

# Governance

The Charter Foundation operates under a formal Cayman legal framework. It is managed by independent, professional directors from Leeward Management Limited and Hash Directors, who specialize in fiduciary services, and who have managed tens of billions of assets on behalf of their clients.

Charter’s governance framework is designed around the following principles:

**Trusted, Independent Governance**. Charter Foundation’s two independent directors act in accordance with fiduciary duties under Cayman Islands law, and are bound by the Foundation’s constitutional documents. This provides builders with confidence that the project is in good hands, but also ensures the ecosystem is protected.

**No Permanent Dependency**. The role of the Charter Foundation, as well as its Facilitating Partner, is temporary and transitional, ending at Release. The builder is not locked into an ongoing relationship with any of the entities involved.

**Separation of Projects**. Each project launched through Charter is structured independently through its own Cayman Launch Company. This ensures there is no commingling of assets, contracts, or liabilities between Chartered projects.

**No Operational or Treasury Control**. The Charter Foundation’s role is limited to governing the launch structure. It does not manage, hold signatory authority over, or otherwise control the builder’s treasury, token supply, distribution, or protocol development. The Charter Foundation does not act as a custodian of digital assets and does not sit on or control project multisignature wallets. Decisions regarding product, tokenomics, treasury, and commercial strategy remain with the builder at all times. This separation is deliberate: it ensures that practical control over the project resides with the builder rather than the Foundation, which both reflects the genuine independence of the structure and supports its characterization with counterparties and regulators.

**Director Decision-Making and Continuity**. Because the Charter Foundation’s directors owe fiduciary duties to the entities they serve, they exercise genuine judgment and may, in appropriate circumstances, decline to approve a proposed action. Charter aligns governance expectations with builders early so that decision rights, approval thresholds, and escalation paths are understood before launch. The framework anticipates the practical situations that arise in governed structures — including a director declining to approve a transaction, a builder wishing to move faster than the board is comfortable with, director resignation, the handling of time-sensitive decisions, and continuity across multiple concurrent projects — and addresses them through defined procedures rather than ad hoc resolution. This is a feature of credible governance, not a constraint on the builder’s independence: the Foundation governs the launch structure, while the builder retains authority over the project’s product, strategy, and timing.


---

# 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.charterfnd.com/technical-documentation/governance.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.