> For the complete documentation index, see [llms.txt](https://community.theiofoundation.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.theiofoundation.org/about-techup/about/hidden/theory-of-change.md). # Theory of Change Version 1.0 | This Theory of Change was approved on DD MMMM YYYY. {% hint style="info" %} [**ShortURL**](https://TIOF.Click/TUTofC) **| Playbook | Assistant** {% endhint %} {% hint style="warning" %} **NOTICE** This documentation page is under construction.\ Should you want to be notified once it's published, [**let us know**](https://TIOF.Click/TIOFTarianUpdatesService). {% endhint %} ## About This section describes the Theory of Change that guides TechUp initiative and its impact. ## The observed problem The IO Foundation has observed the following problems: \[Work in Progress] * Support and train technologists in their role as NextGen Rights Defenders * Enable and organize participation in key working groups to prevent Digital Harms and implement Digital Rights by design * Provide a space for Tech NGOs to be born and supported ## The proposed solutions The IO Foundation proposes the following solutions to the observed problems. \[Work in Progress] ## Theory of change The IO Foundation proposes the following Theory of Change to address the observed problems. \[Work in Progress] --- # 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://community.theiofoundation.org/about-techup/about/hidden/theory-of-change.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.