> For the complete documentation index, see [llms.txt](https://cqube.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cqube.sunbird.org/techanical-overview/design-principles.md).

# Design Principles

* **Low Tech/Minimal Coding:** Leverage existing tools and provide configuration options to minimize the need for coding.
* **API First:** Design APIs for all functionality and blocks to enable independent evolution and integration.
* **Progressive Enhancement:** Allow for module changes and tiered improvements in the user experience.
* **Modularity:** Design modular blocks that can be selected and integrated based on specific needs.
* **Integrations:** Enable integration of higher-order capabilities through clear boundaries and APIs.
* **Ease of Deployment/Management:** Provide easy deployment options and support on commodity hardware or cloud platforms.
* **Scalable:**
  * **Ingestion:** Design scalable ingestion processes for real-time data updates.
  * **SLA Driven:** Strive for a 30-minute SLA between data ingestion and insight generation.
* **Performance:** Prioritize stable performance within specified hardware limitations.
* **Data Privacy:** Store only aggregated data and insights, ensuring no personally identifiable information is stored.
* **Accessibility:** Ensure accessibility on mobile and desktop devices.
* **Data Security:** Implement specific measures to safeguard data (further details required).

These design considerations aim to create a configurable, scalable, and user-friendly solution for effective data-driven governance in the education sector.

The detailed design principles of cQube, according to the architecture, can be found [here](https://project-sunbird.atlassian.net/wiki/spaces/CQUB/pages/3258024044/cQube+Design+Document+Nov+2022#3.-Design-Considerations).


---

# 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://cqube.sunbird.org/techanical-overview/design-principles.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.