> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/platform/deep-dive/principles.md).

# Principles

The foundational approach and design principles of the DIGIT platform

#### DIGIT platform design principles

<table data-card-size="large" data-view="cards"><thead><tr><th></th></tr></thead><tbody><tr><td><p><strong>Single Source of Truth</strong>  </p><p></p><p>Shared data registries ensure data is updated and reused without duplicating transactional data. DIGIT registries offer standard API access that multiple service providers can leverage.</p></td></tr><tr><td><p><strong>Security and Privacy</strong> </p><p></p><p>DIGIT is designed to be secure by default featuring configurable role-based access. Personally Identifiable Information (PII) is encrypted and inaccessible by analytical systems.</p></td></tr><tr><td><p><strong>Scalability</strong> </p><p></p><p>DIGIT is built for scale. Its event-driven asynchronous microservices architecture enables DIGIT to handle millions of service requests with ease.</p></td></tr><tr><td><p><strong>Flexible</strong> </p><p></p><p>DIGIT adopts a multi-user approach. Users (agencies or service providers) have the provision to configure their master data and workflows. They also have the flexibility to develop and implement custom service versions.</p></td></tr><tr><td><p><strong>Modular</strong> </p><p></p><p>DIGIT components are designed as modular microservices with interoperable APIs. Each service can be scaled, updated and deployed autonomously, independent of others.</p></td></tr><tr><td><p><strong>Interoperable</strong> </p><p></p><p>API first design and use of Open Standards wherever possible ensures DIGIT is interoperable with other systems. Data can be exchanged seamlessly as and when required.</p></td></tr><tr><td><p><strong>Ease of Access</strong> </p><p>DIGIT enables easy access to all stakeholders including citizens, employees, administrators, developers or system administrators. Data available through API can be routed to specific applications on the web, mobile, or chat.</p></td></tr><tr><td><p><strong>Open</strong> </p><p>DIGIT is open source and uses open source technologies and standards to ensure that data and core services are never vendor locked-in. MIT License gives rights to any agency or its partners to copy the source code and deploy it for their needs.</p></td></tr></tbody></table>


---

# 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.digit.org/platform/deep-dive/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.
