> For the complete documentation index, see [llms.txt](https://patterns.innersourcecommons.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://patterns.innersourcecommons.org/gl/explore-patterns.md).

# Explore os modelos

A comunidade InnerSource Commons aporta cada vez máis modelos a este libro; o que é incrible!

Pero, como facilitar que os/as lectores/as descubran os modelos que poden axudalos/as na súa situación particular?

Para isto proporcionamos este mapa conceptual, que **clasifica os modelos en función das diferentes fases dun programa InnerSource** e dos desafíos que poden xurdir nas respectivas fases.

![Mapa conceptual dos modelos InnerSource](https://759310253-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FptpH83yl04rC7Zlp54rN%2Fuploads%2Fgit-blob-a01eb09c953b07383c6598c865015169dd8886b9%2Finnersource-program-mind-map.png?alt=media)

## Mellore este mapa conceptual

Se vostede detecta algo neste mapa conceptual que lle resulta incorrecto, pode [abrir unha incidencia](https://github.com/InnerSourceCommons/InnerSourcePatterns/issues) na que describa o problema xunto co arranxo que se debería levar a cabo.

Ademais, se ten outras ideas para dar a coñecer estes modelos ou desexa mellorar este mapa conceptual, revise a documentación do noso enfoque de [Categorización de modelos](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/pattern-categorization/README.md) e verifique como [contribuír a este libro](/gl/contribute.md).

## Referencias

A idea de categorizar modelos como este baséase, parcialmente, na descrición en [*Thoughts on an InnerSource Pattern Language*](https://drive.google.com/file/d/13AY8glCOdpLOVuz7cVD6QOB8d2xbHCS1/view) \[Reflexións arredor do modelo InnerSource] de Tim Yao, Bob Hanmer e Padma Sudarsan (2018). Para obter máis detalles, pode consultar a diapositiva 15 da presentación.


---

# 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://patterns.innersourcecommons.org/gl/explore-patterns.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.
