> For the complete documentation index, see [llms.txt](https://docs.cortex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortex.io/solutions/production-readiness.md). # Production readiness Production readiness is the state in which a software system is fully prepared to operate reliably in a live production environment. A well-defined production readiness process minimizes deployment risks, enhances system stability, and accelerates issue resolution, ultimately leading to a better user experience and more efficient software delivery cycles.
Use Scorecards to measure Production Readiness.
### How Cortex helps with production readiness Your organization can drive production readiness in Cortex by: * Codifying engineering standards in Scorecards and continuously evaluating entities against standards using live data from integrated tools * Automating production readiness requirements in new services and infrastructure via Workflows * Setting up data verification processes to ensure accuracy across your catalogs {% hint style="success" %} Looking for additional resources on enforcing Production Readiness in Cortex? Check out the [Cortex Academy "Production Readiness" course](https://academy.cortex.io/courses/production-readiness), available to all Cortex customers and POVs. {% endhint %} ## Drive and maintain production readiness in Cortex Learn how to use Cortex features for production readiness: [**Standardize and automate readiness**](/solutions/production-readiness/configure.md). Learn about maintaining readiness and continuously improving: [**Production Readiness in action**](/solutions/production-readiness/in-action.md). --- # 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.cortex.io/solutions/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.