---
title: "Praxis for quality leaders"
route: "/for/quality-lead"
description: "Quality Harness reviews individual changes; a separate private Quality Platform is planned for history within and across projects."
template: role
intent: "Help a quality lead see and act on AI code quality drift."
parent: "/for"
primaryCta: { label: "Talk to us about private access", href: "/enterprise?interest=quality-platform#contact" }
schemaType: Service
hero:
  eyebrow: "Quality Lead"
  headline: "See quality drift before AI code makes it the new baseline."
  sub: "Review volume can rise while quality and security movement after merge stays invisible. Quality Harness reviews one result; the private Platform direction addresses history across projects."
  primaryCta: { label: "Talk to us about private access", href: "/enterprise?interest=quality-platform#contact" }
sections:
  - { id: pain, kind: pain, heading: "The baseline changes between review meetings" }
  - { id: why-diff-review-is-not-enough, kind: explanation, heading: "Why diff review is not enough" }
  - { id: two-controls, kind: quality, heading: "Two needs, two product levels" }
  - { id: drift-example, kind: cards, heading: "A drift signal with an owner" }
  - { id: access, kind: proof, heading: "Private Quality Platform access" }
  - { id: next-step, kind: cta, heading: "Discuss the delivery flow" }
---

## The baseline changes between review meetings

You can have a strong review of each change and still lack a view of what repeated changes are doing to the codebase. A single result tells you what was checked for that work package. Drift requires comparable observations over time.

## Why diff review is not enough

One review cannot establish a trend, and a green label does not mean every test or security check ran. Read the evidence, including failures and skipped checks, before applying a Quality outcome. A separate history is needed to see repeated patterns within each project.

## Two needs, two product levels

**Quality Harness** is the delivered fourth role. It reviews a particular implementation and its evidence, reports findings, previews application and applies an approved result where configured. A reviewer verdict, applied status, Git publication and merge are distinct events. [Read its guide](/docs/plugins/quality).

**Quality Platform** is the separate private product direction. It is planned to retain each project's quality history and provide oversight across multiple projects, including drift against a chosen default-branch baseline. The chart on this page is illustrative, not live telemetry from the inspected repositories.

## A drift signal with an owner

- **Observation** — record a comparable measure for a particular project and revision.
- **Trend** — compare repeated observations within that project before calling a movement drift.
- **Investigation** — inspect associated findings to decide what action and owner make sense; a score alone does not prove root cause.

## Private Quality Platform access

Discuss the projects and history you need to track. Private Platform availability and integrations are arranged with the team; the Harness has its own role distribution and is not defined by the Platform access gate.

## Discuss the delivery flow

Bring one recent review and one longer-running quality concern. We can map the individual review and the planned history separately.