> For the complete documentation index, see [llms.txt](https://inquiry.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inquiry.sunbird.org/learn/product-and-developer-guide/question-and-question-set-service/source-code.md).

# Source Code

Here is the link to the source code. Currently, inQuiry leverages source code from [Sunbird Knowlg](https://knowlg.sunbird.org/learn/readme) for core component (ontology-engine). For Branch and Tag, Please checkout release notes.

\
\
**Question & QuestionSet Service Source Code:** 

{% embed url="<https://github.com/Sunbird-inQuiry/inquiry-api-service.git>" %}

{% embed url="<https://youtu.be/yoHBowTh4OQ?si=OddNJ_r67qgGSyWV&t=37>" %}

**Core Component (knowlg-core) Source Code:**&#x20;

{% embed url="<https://github.com/Sunbird-Knowlg/knowledge-platform.git>" %}

For Question & QuestionSet Service, Please use [**assessment-api** ](https://github.com/Sunbird-inQuiry/inquiry-api-service/tree/master/assessment-api)folder in above repo.&#x20;

**Asynchronous Flink Job Source Code:**

{% embed url="<https://github.com/Sunbird-inQuiry/data-pipeline.git>" %}

Question & QuestionSet Service uses below async jobs (written using Apache Flink)&#x20;

1. [async-questionset-publish](https://github.com/Sunbird-inQuiry/data-pipeline/tree/master/publish-pipeline/async-questionset-publish) : used for publish operation of Question & QuestionSet Asset.

{% embed url="<https://youtu.be/yoHBowTh4OQ?si=il_JPSlJU_FGB4DD&t=1433>" %}


---

# 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://inquiry.sunbird.org/learn/product-and-developer-guide/question-and-question-set-service/source-code.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.