> For the complete documentation index, see [llms.txt](https://handbook.proanimal.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.proanimal.org/other/corporate/bylaws/article-ii-offices.md).

# Article II: Offices

#### Section 2.1 Business Offices.

The principal office of the Organization in the State of Colorado shall be at such location as the Mission Circle shall determine. The Organization may have such other offices, either within or without the State of Colorado, as the Mission Circle may determine from time to time. 

#### Section 2.2 Registered Office.

The Organization shall have and continuously maintain in the State of Colorado a registered office, and a registered agent whose office is identical with such registered office. The registered office may be, but need not be, identical with the principal office of the Corporation in the State of Colorado. The registered agent and the address of the registered office may be changed from time to time by the Mission Circle.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://handbook.proanimal.org/other/corporate/bylaws/article-ii-offices.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.