> For the complete documentation index, see [llms.txt](https://docs.taxaible.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taxaible.co/readme/platform-overview.md). # Platform Overview High-level Platform Vision TaxAible is built on a robust architecture designed for accuracy, security, and ease of use. ### Core Pillars #### 1. AI-First Logic Unlike traditional tax software that relies on static forms, TaxAible uses Generative AI and advanced proprietary models to interpret Pakistani tax law. This allows for a more natural interaction where the system understands context and nuances. #### 2. IRIS Integration The biggest pain point in Pakistani tax filing is the FBR IRIS portal. TaxAible solves this with the **IRIS Connector**, a browser extension that maps your calculated tax data directly into the IRIS form fields, saving hours of manual data entry. #### 3. Data Privacy We encrypt sensitive information and use secure database practices. Your tax data is yours alone, and we only use it to help you prepare your returns. #### 4. Continuous Updates Tax laws in Pakistan change frequently. TaxAible's AI engine is regularly updated with the latest Finance Acts and SROs to ensure compliance with current regulations. --- # 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.taxaible.co/readme/platform-overview.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.