> For the complete documentation index, see [llms.txt](https://docs.frequencychain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frequencychain.org/16.-best-practices-security-and-production-readiness.md). # 16. Best Practices, Security, and Production Readiness Building applications on FreCx requires more than functional correctness. Production-grade systems must be designed to ensure security, reliability, scalability, and observability. This section outlines the essential practices that developers and infrastructure operators must follow when moving from development environments to production deployments. FreCx provides a robust foundation through its architecture and consensus model. However, the responsibility of building secure and resilient applications ultimately lies with developers. This includes safeguarding assets, ensuring deterministic execution, and maintaining operational stability across all layers of the system. --- # 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.frequencychain.org/16.-best-practices-security-and-production-readiness.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.