{
  "id": "page:qa",
  "_kind": "Page",
  "_file": "wiki/qa/README.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "title": "Quality, Verification, and Delivery",
    "displayName": "Quality, Verification, and Delivery",
    "slug": "qa",
    "articlePath": "wiki/qa/README.md",
    "article": "# Quality, Verification, and Delivery\n\nTests, evidence-boundary checks, versioning, CI/CD, and downstream artifact distribution. The phase that **enforces** every guarantee the earlier phases promise.\n\n## Files in this directory\n\n| Path | Purpose |\n|---|---|\n| [`00-qa-architecture.md`](./00-qa-architecture.md) | Test pyramid, evidence-boundary checks, regression detection. |\n| [`01-versioning-and-delivery.md`](./01-versioning-and-delivery.md) | Schema semver, downstream artifact tagging, release pipeline, consumer pinning. |\n| [`02-cicd.md`](./02-cicd.md) | CI gates, CD pipeline, promotion environments. |\n| [`03-coverage.md`](./03-coverage.md) | Coverage definitions across the catalog. |\n| [`04-evidence-boundaries.md`](./04-evidence-boundaries.md) | Where graph claims meet external truth; staleness detection; refresh. |\n| `tests/` | Test fixtures, integration harnesses, e2e scripts. |\n\n## Acceptance\n\n- Every NodeKind has at least one test.\n- Every generator has an integration test against a known graph fixture.\n- E2E tests cover key user flows (schema change → regenerated docs → SDK consumer compiles).\n- CI gates schema/graph PRs on validator + invariant + freshness checks.\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:views-quality-tower",
      "to": "page:qa",
      "kind": "documents"
    }
  ]
}