> For the complete documentation index, see [llms.txt](https://governance.tomediaarts.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://governance.tomediaarts.org/board-structure-and-roles/board-procedures/governance-policy.md).

# Governance Policy

The Board will govern with a style which emphasizes outward vision, encouragement of diversity in viewpoints, strategic leadership, clear distinction of Board and Staff Roles, collaborative decision-making, a focus on the future and proactivity.

The Board will:

* Be accountable for the realization of its goals.
* Direct, control and inspire the organization through careful establishment of the broadest written policies which reflect the values and perspectives of its members and stakeholder communities.
* Monitor and regularly discuss the Board’s own process and performance to ensure the continuity of its governance capability by retention and development of Board members.
* Self-evaluate its performance.
* Commit to continuous improvement, including orientation of new members and Directors to the Board’s governance model and periodic Board discussion of governance process.


---

# 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://governance.tomediaarts.org/board-structure-and-roles/board-procedures/governance-policy.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.
