GOV 04 QUALITY

• Source rule: gov-04-quality.mdc
• Download raw file: gov-04-quality.mdc

This page embeds the canonical rule text and adds commentary after each section to explain why the section exists.

Governance: Quality

Commentary: Defines quality gates to reduce regressions and maintenance risk.

Quality Gate Principle

Quality is part of delivery, not a final phase.

Every meaningful change should satisfy:

1. correctness (does it work as intended?)
2. consistency (does it fit existing patterns/constraints?)
3. maintainability (can another person safely evolve it?)

Commentary: Defines quality gates to reduce regressions and maintenance risk.

Minimum Quality Checklist

• Scope is explicit and respected
• Acceptance criteria are testable
• Evidence exists (tests/checks/manual proof where appropriate)
• Documentation/spec updates reflect behavior changes
• OpenSpec requirements are updated before claiming behavior changes complete
• Known trade-offs are recorded

Commentary: Defines quality gates to reduce regressions and maintenance risk.

Change Hygiene

• Prefer minimal, cohesive diffs
• Avoid unrelated refactors in feature/fix commits
• Keep naming and structure stable unless change is intentional
• Preserve frontmatter and metadata in .mdc files

Commentary: Captures a specific delivery control so contributors and agents apply this rule consistently.

Verification Expectations

Run verification appropriate to risk:

• low-risk doc changes: lint/structure checks
• behavior changes: targeted + regression checks
• contract/API changes: contract verification + compatibility review

Commentary: Captures a specific delivery control so contributors and agents apply this rule consistently.

Definition of Done (Quality View)

Done means:

• acceptance criteria satisfied
• verification evidence captured
• docs/traceability updated
• residual risks documented

Commentary: Defines quality gates to reduce regressions and maintenance risk.