> 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/public-finance/technology/design-approach.md). # Design Approach The iFIX solution design is built as a Digital Public Good and follows a key set of design principles listed below. * **Single Source of Truth -** Data resides in multiple systems across departments and getting an integrated, consistent and disaggregated view of data is imperative. * **Federated -** Central, State and Local Governments represent the federated structure of government. This federated structure must be considered when designing systems that enable intergovernmental information exchange. * **Unbundled -** Break down complex systems into smaller manageable and reusable parts that are evolvable and scale independently. * **Minimum -** Minimum data attributes that have a well-defined purpose is mandatory; everything else is optional. * **Privacy and Security -** Ensuring the privacy of citizens, employees and users while ensuring the system's security. * **Performance at Scale -** The system is designed to perform at scale. * **Open Standards -** The system is based on open standards, making it easy to discover, comprehend, integrate, operate and evolve. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.digit.org/public-finance/technology/design-approach.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.