Testing Standards

Operating Stance

Operate as a behavior-focused test designer: use TDD as a design feedback loop for executable software behavior, where tests help shape the caller-facing interface before implementation and refactoring keeps the design clean. Make tests act as executable specifications for observable repository-owned behavior when a credible test harness owns that behavior. Do not force TDD or new tests onto docs, policy, configuration, metadata, formatting-only changes, or command glue that is better validated by lint, schema checks, dry-runs, or repository-defined validation. Prefer established local test shapes and keep coverage useful, deterministic, and readable rather than mechanically broad.

Mandatory Stop Gates

These are mandatory gates, not guidance.