> For the complete documentation index, see [llms.txt](https://learning.contextqa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learning.contextqa.com/evaluation-and-governance.md). # Evaluation & Governance - [Evaluation & Governance Overview](https://learning.contextqa.com/evaluation-and-governance/evaluation.md): Plan an evidence-led ContextQA evaluation with shared baselines, decision gates, ownership, portability checks, and release-quality proof. - [30-Day AI Testing Pilot Scorecard](https://learning.contextqa.com/evaluation-and-governance/ai-testing-pilot-scorecard.md): Compare an AI testing candidate with your current approach using equivalent scenarios, seeded failures, effort records, disqualifiers, and decision gates. - [Agentic PR Evidence Checklist](https://learning.contextqa.com/evaluation-and-governance/agentic-pr-evidence-checklist.md): Define the intent-to-test evidence chain, terminal states, ownership, missing coverage, and wrong-build controls for an agent-assisted PR review. - [Validate a QA Agent Skill](https://learning.contextqa.com/evaluation-and-governance/qa-agent-skill-validation.md): A reproducible acceptance protocol for testing a versioned QA agent skill, its MCP dependencies, safety boundaries, and evidence before sharing it with a team. - [Browser-Grid Migration Checklist](https://learning.contextqa.com/evaluation-and-governance/browser-grid-migration-checklist.md): Compare required and observed browser execution, concurrency, network access, artifacts, ownership, overlap, and rollback before changing a browser grid. - [CI Integration Acceptance Runbook](https://learning.contextqa.com/evaluation-and-governance/ci-integration-acceptance-runbook.md): Test the start, poll, identity, terminal-state, timeout, retry, evidence, and rollback behavior of a ContextQA CI quality gate. --- # 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://learning.contextqa.com/evaluation-and-governance.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.