> For the complete documentation index, see [llms.txt](https://ed.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ed.sunbird.org/older-versions/contribute/source-code/workflows/manage-learn/ml-report-service/user-flow-diagram.md).
# User Flow Diagram
Within the ML Projects service, once a user has successfully concluded a project, they can subsequently make use of the ML Reports service. This specialized service is designed to provide users with comprehensive and detailed reports regarding their project submissions.
Through the utilization of the ML Reports service, users have the capability to request observation reports for the submissions they have made. These reports are generated by extracting relevant data from Druid, which is then used to compile and create detailed observation reports.
Through the utilization of the ML Reports service, users have the capability to request survey reports for the submissions they have made. These reports are generated by extracting relevant data from Druid, which is then used to compile and create detailed survey reports.
---
# 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://ed.sunbird.org/older-versions/contribute/source-code/workflows/manage-learn/ml-report-service/user-flow-diagram.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.
.png?alt=media)
.png?alt=media)