# V2 No-Stub Quality Oath

Production quality is a wellness issue. Hidden stubs create last-minute rescue
work, break trust across disciplines, and convert preventable ambiguity into
crunch. V2 keeps partial work unchecked until it is implemented, verified, and
owned.

## Oath

Every checked task must be verified in code, content, documentation, contract,
or automation appropriate to the task. Placeholders, fake integrations, silent
TODOs, disabled validators, and unowned follow-up work cannot be counted as
complete.

## Required Evidence

A checked task needs:

- implementation artifact
- verification command or automation gate
- owner
- release-gate evidence where applicable
- rollback or remediation path when the feature is operational

## Stub Review

Reviewers search for explicit placeholders and silent stubs before signoff.
Allowed scaffolding must be named, tracked, owned, and left unchecked in
`V2/V2_TODOS.md`. No one is expected to fill hidden gaps through overtime.

## Escalation

When a stub is found after signoff, the owner records the incident, unchecks the
affected task if needed, scopes the missing work, and raises schedule or scope
risk before asking the team for overtime.