> For the complete documentation index, see [llms.txt](https://docs.landscale.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.landscale.org/landscape-initiative-maturity/collective-goals-and-actions.md). # Collective goals and actions The collective goals and actions criterion evaluates whether stakeholders in the landscape initiative have established a shared vision by defining long-term sustainability goals at the landscape scale. It also assesses whether they have developed a collective action plan and a strategy for securing the necessary funding and resources to achieve these goals. Strong collective sustainability goals should be evidence-based and address the holistic dimensions of landscape sustainability. To effectively drive progress toward these goals, initiatives should have a robust collective action plan that addresses systemic issues linked to the goals through clear strategies and actions, along with a structured funding and finance strategy that identifies potential (preferably diversified) sources to ensure sustained implementation over time. To assess these aspects, the criterion is divided into three sub-criteria: 1. [Collective sustainability goals](/landscape-initiative-maturity/collective-goals-and-actions/collective-sustainability-goals.md). 2. [Collective action plan](/landscape-initiative-maturity/collective-goals-and-actions/collective-action-plan.md). 3. [Funding and finance strategy](/landscape-initiative-maturity/collective-goals-and-actions/funding-and-finance-strategy.md). --- # 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://docs.landscale.org/landscape-initiative-maturity/collective-goals-and-actions.md?ask=&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.