QA

Key Ideas

• Quality Evidence: QA gathers proof that the work behaves as intended.
• Project Specific: QA should use target-app checks, guidance, and governance.
• Failure Is Useful: failed QA should create actionable evidence, not just block progress.

Purpose

QA exists to turn confidence into evidence. Refine should make agent-produced work accountable through tests, checks, diagnostics, review aids, and other target-app verification.

Expected Role

QA should connect workflow to the Agents capability's quality, governance, logs, and evidence behavior. It should record what ran, what passed, what failed, and what should happen next.

QA should be flexible. Some apps need automated tests, some need build checks, some need visual inspection, and future agents may generate targeted verification for the Gap.

What Happens

When a Gap is in QA:

• Refine gathers quality evidence for the change.
• It may run configured target-app tests, generated checks, diagnostics, governance review, visual checks, or other project-specific verification.
• Checks should run through shared Process and Agents capabilities where commands or agents are involved.
• Results should attach to the Gap as evidence: what ran, what passed, what failed, and what risk remains.
• Passing QA should move the Gap toward review or completion according to workflow rules.
• Failing QA should preserve output and create a recovery path rather than losing the failed attempt.

Future Direction

Future QA should become more agentic: generated tests, screenshot comparison, semantic checks, dependency analysis, risk scoring, and evidence summaries. The state should remain the workflow point where proof is gathered.