---
title: "Quality Harness and Quality Platform — Praxis"
route: "/platform/quality"
description: "Quality Harness reviews individual work; a separate private Quality Platform is planned to retain quality history across projects."
template: quality-platform
intent: "Explain private Quality Platform access for merge control and baseline drift visibility."
parent: "/platform"
primaryCta: { label: "Talk to us", href: "/enterprise?interest=quality-platform#contact" }
schemaType: Service
hero:
  eyebrow: "Quality Harness · private Platform direction"
  headline: "Review one result. Build a history across projects."
  sub: "Quality Harness reviews a particular work result. A separate private Quality Platform is planned for each project’s quality history and oversight across projects."
  primaryCta: { label: "Talk to us", href: "/enterprise?interest=quality-platform#contact" }
  secondaryCta: { label: "Read the Quality Harness guide", href: "/docs/plugins/quality" }
sections:
  - { id: visibility-gap, kind: pain, heading: "The quality signal missing from faster delivery" }
  - { id: harness, kind: quality, heading: "Quality Harness: inspect one work result" }
  - { id: platform, kind: quality, heading: "Quality Platform: planned project histories" }
  - { id: drift-model, kind: cards, heading: "A drift model that guides investigation" }
  - { id: connection-model, kind: explanation, heading: "Connect quality to the delivery flow" }
  - { id: private-access, kind: cta, heading: "Request private access" }
---

## The quality signal missing from faster delivery

A quality leader needs to distinguish two questions: does this particular implementation have adequate evidence, and are repeated changes shifting the quality of each codebase over time? One local review answers only the first. The second requires comparable historical observations within each project.

## Quality Harness: inspect one work result

The delivered Quality Harness is the fourth role in the BA → Architect → Developer → Quality Harness chain. It opens the relevant package, implementation and evidence; reports findings and its operation-specific verdict; then previews how a result would be applied. Applying that outcome is a separate approved action where the integration is configured. It does not merge the code or establish a live trend dashboard. [Read the Quality role guide](/docs/plugins/quality).

## Quality Platform: planned project histories

The separate private Quality Platform is planned to retain quality observations for Project A, Project B and other projects, preserving each project’s history and providing a cross-project view. The direction includes baseline and drift tracking. Recurring evaluations and a project dashboard are part of that direction. Talk with us about the access and integrations your team needs.

## A drift model that guides investigation

- **Trend** — compare repeated observations against a chosen default-branch baseline within the same project.
- **Threshold** — make a meaningful movement visible against agreed criteria.
- **Investigation** — use findings to decide what to inspect next; a score alone does not prove root cause or owner.

Any chart on this page illustrates the intended model, not live telemetry or a deployed production service.

## Connect quality to the delivery flow

Quality Harness can inspect one Developer result before any approved publication. A future Platform history would add longitudinal context for that project and an overview across projects. Start with the Quality Harness guide for individual reviews, or talk with us about the private Platform.

## Request private access

Tell us which projects, baselines and quality questions you need to track. We can discuss the private Platform direction and configured access.