# 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: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://cqube.sunbird.org/techanical-overview/design-principles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.