---
title: 'For quality leads: see quality drift before it settles in'
description: 'Review one result with the Quality Harness, read the failures and skipped checks, and see where a planned private Platform would track drift across projects.'
url: 'https://flagridge.com/for/quality-lead'
type: 'audience'
template: 'role'
language: 'en'
---

# See quality drift before AI code makes it the new baseline.

> 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.

Primary action: [Talk to us about private access](https://flagridge.com/enterprise?interest=quality-platform#contact)

## 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](https://flagridge.com/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.

---
HTML: https://flagridge.com/for/quality-lead
Markdown: https://flagridge.com/for/quality-lead.md