> For the complete documentation index, see [llms.txt](https://comun.gitbook.io/inicio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://comun.gitbook.io/inicio/04.-metodologia/1.-definicion-de-instituciones-y-sistemas-que-observamos.md).

# 1. Definición de instituciones y Sistemas que observamos

El Observatorio monitorea, evalúa y certifica a los 32 Sistemas Estatales Anticorrupción y al Sistema Nacional Anticorrupción, en su conjunto, así como a cada [Sujeto Obligado](#user-content-fn-1)[^1] o institución que los conforma. Éstos son:

1. Las Secretarías Ejecutivas o Técnicas 
2. Los Comités de Participación Ciudadana
3. Las Comisiones de Selección
4. Los Comités Coordinadores
5. Las Fiscalías Anticorrupción

[^1]: Según la Ley General de Transparencia y Acceso a la información Pública los sujetos obligados son: “cualquier autoridad, entidad, órgano y organismo de los Poderes Ejecutivo, Legislativo y Judicial, órganos autónomos, partidos políticos, fideicomisos y fondos públicos, así como cualquier persona física, moral o sindicato que reciba y ejerza recursos públicos o realice actos de autoridad en los ámbitos federal, de las Entidades Federativas y municipal.”


---

# 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://comun.gitbook.io/inicio/04.-metodologia/1.-definicion-de-instituciones-y-sistemas-que-observamos.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.