> For the complete documentation index, see [llms.txt](https://docs.freedomtechhq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.freedomtechhq.com/readme.md). # Freedom Documentation Welcome to the Freedom docs! This guide helps you navigate our documentation structure. ## What's Where ### Top-Level Folders * **Architecture/** - System design, component relationships, and technical decisions * **Processes/** - Business-process guidelines. Written for both people and AI-agents * **\[Feature Name]/** - Documentation for a specific feature * [**Store**](broken://pages/4vk0Nxtd7bZLHSxBVch9) - Encrypted synchronized file store, the core of our system * **Email** - Encrypted email service ### Key Documents * [**/How to Write Good Docs.md**](/how-to-write-good-docs.md) - Guidelines for contributing to documentation * **\[Feature Name]/! Start Here.md** - Noticeable entry point, organized links to other docs * **\[Feature Name]/! FUNCTIONAL COVERAGE.md** - Test planning and coverage tracking ## How to Work With `/docs` Open the folder with Obsidian. Recommended plugins: * Smart Typography We use MDX format (Markdown with YAML metadata). ## Supporters Thank you to [GitBook](https://www.gitbook.com/) for hosting our docs at [https://docs.FreedomTechHQ.com](https://docs.freedomtechhq.com)! --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.freedomtechhq.com/readme.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 `build a script that syncs our docs to a CMS` 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.