Independent QA needs a veto and an override path.

Video caption

Independent QA needs a veto and an override path.

A green status has an issuer and scope.

The missing test is not a failing test or a passing one.

My rule: No invisible bypass.

#EricFieldNotes

Full written post / accessibility read

A QA agent can generate insightful probes, but it is not independent if the coding worker can alter its rubric, replace its check or merge through a warning. I want a gate under separate authority that rejects failed or missing required evidence for the exact artifact. A named person may override only through a recorded, bounded exception.

GitHub rulesets can require named checks from an expected app, but that only protects status provenance. The fixture still needs an independent product oracle, fresh non-empty result and digest match. For the fictional tenant exception, test both allowed and forbidden cohorts, then make a disposable wrong patch turn the gate red.

Argo Rollouts distinguishes success, failure and inconclusive analysis. Apply that discipline to local and operational evidence: stale report, empty fixture or insufficient affected canary cohort means the release owner lacks a verdict. Pause the release or record a transparent override with scope and compensation.

Define who can override, for which cohort, until when, with what rollback signal and how the missing evidence will be acquired. Do this because a QA veto without accountable exceptions can freeze useful work, while exceptions without receipts can erase the gate altogether.

#EricFieldNotes

Four-beat scene transcript

1. Independent QA needs a veto and an override path.

A QA agent can generate insightful probes, but it is not independent if the coding worker can alter its rubric, replace its check or merge through a warning. I want a gate under separate authority that rejects failed or missing required evidence for the exact artifact. A named person may override only through a recorded, bounded exception.

Visual: Both must be designed before agents scale.

2. Make check provenance visible.

GitHub rulesets can require named checks from an expected app, but that only protects status provenance. The fixture still needs an independent product oracle, fresh non-empty result and digest match. For the fictional tenant exception, test both allowed and forbidden cohorts, then make a disposable wrong patch turn the gate red.

Visual: A green status has an issuer and scope.

3. Treat unverified as a first-class stop.

Argo Rollouts distinguishes success, failure and inconclusive analysis. Apply that discipline to local and operational evidence: stale report, empty fixture or insufficient affected canary cohort means the release owner lacks a verdict. Pause the release or record a transparent override with scope and compensation.

Visual: The missing test is not a failing test or a passing one.

4. Design the exception before the emergency.

Define who can override, for which cohort, until when, with what rollback signal and how the missing evidence will be acquired. Do this because a QA veto without accountable exceptions can freeze useful work, while exceptions without receipts can erase the gate altogether.

Visual: No invisible bypass.

Research and claim limits

• GitHub Docs: ruleset required status checks (S146)
• Argo Rollouts: analysis overview (S148)
• NIST SP 800-218 Secure Software Development Framework (S150)

The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.