> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/interoperability/integrations/mosip-crvs-integration/integration-overview-and-context.md).

# Integration Overview and Context

### What is covered in sub-sections

This section establishes the foundation for understanding MOSIP-CRVS integration. It covers:

* [**Core Integration Principles**](/1.2.0/interoperability/integrations/mosip-crvs-integration/integration-overview-and-context/core-integration-principles.md): The fundamental architectural and operational principles that guide how MOSIP and CRVS systems interact, including system roles, data flow patterns, and coordination mechanisms.
* [**Integration Boundaries & Real-World Implications**](/1.2.0/interoperability/integrations/mosip-crvs-integration/integration-overview-and-context/integration-boundaries-and-real-world-implications.md): The rationale behind integration scope decisions, explaining why certain limitations exist and how they protect individual rights, maintain system integrity, and respect the distinct mandates of Foundational ID and Civil Registration systems.


---

# 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.mosip.io/1.2.0/interoperability/integrations/mosip-crvs-integration/integration-overview-and-context.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.