# Code Review and Quality Gates ### Purpose Code review and quality gates reduce defects, improve maintainability, and support assurance. ### Code Review Criteria Reviewers should check: * correctness * readability * maintainability * security * test coverage * performance implications * dependency changes * architectural fit * documentation updates ### Quality Gates Quality gates may include: * peer review completed * automated tests passed * security scan completed * dependency check completed * accessibility check completed where applicable * deployment test completed * release approval recorded ### Operating Rule No material code should be released without appropriate review and evidence. --- # Agent Instructions: 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: ``` GET https://framework.aic.io/company-operating-manual/engineering-and-technical-standards/code-review-and-quality-gates.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.