> For the complete documentation index, see [llms.txt](https://chusdrter.gitbook.io/chusdrter-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chusdrter.gitbook.io/chusdrter-docs/introduction/readme.md). # What is Charter > Charter is a treasury operations layer for Stellar-based organizations. Instead of a bare multisig wallet, funds are held under a policy contract with defined budget categories, spend limits, and approval thresholds. Contributors submit disbursement requests against a category; designated approvers sign off within the policy's rules; once the threshold is met, funds release automatically. Every category, request, and disbursement is publicly readable on-chain. > > Charter is two things: a `treasury` contract, one instance per organization, that holds the actual policy and funds; and a `factory` contract that deploys new treasury instances and keeps a public registry of every organization using Charter. ## Two contracts, one system An organization's treasury and the factory that created it do different jobs. The **treasury** is where an organization's money and rules live. One treasury belongs to one organization. It holds a single token, tracks that organization's budget categories and their caps, keeps the approver list and the approval threshold, and records every disbursement request and its approvals. Reads and writes for day-to-day operations go straight to the treasury. The **factory** deploys treasuries and keeps a registry of them. Every treasury is deployed from the same reviewed contract code, so an outside observer can confirm that every organization on Charter runs identical rules. The factory is the only part of the system involved in creating a treasury; after that, an organization interacts with its own treasury directly. ## Who this documentation is for * **Organization admins** set up a treasury, define budget categories, and manage the approver set. Start with [Getting Started](/chusdrter-docs/for-organization-admins/getting-started.md). * **Approvers and requesters** submit disbursement requests and sign off on them. Start with [Submitting a Request](/chusdrter-docs/for-approvers-and-requesters/submitting-a-request.md). * **Developers and reviewers** evaluating the code will find the contract reference under [Smart Contracts](/chusdrter-docs/smart-contracts/overview.md) and integration details under the [Developer Guide](/chusdrter-docs/developer-guide/local-setup.md). Charter runs on Stellar testnet and has not been audited. It is experimental software; do not use it to custody real value. --- # 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://chusdrter.gitbook.io/chusdrter-docs/introduction/readme.md?ask=&goal= ``` `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.