# Validation Architecture — {{phase_name}}

<!-- Generated by /rcode-plan --research. Dimension 8 (Nyquist Compliance) reads this file. -->
<!-- Delete this comment block after filling in. An empty VALIDATION.md causes Dimension 8e to BLOCK. -->

**Phase:** {{phase_id}}
**Generated:** {{date}}

## Validation Architecture

<!-- Describe how this phase will be validated. What tests exist or will be created? -->
<!-- If no test files are planned, explicitly state why and what manual checks substitute. -->

### Test Strategy

| Concern | Test File | Command | When Run |
|---------|-----------|---------|----------|
| {{feature/requirement}} | {{test_file_path}} | {{run_command}} | Wave {{N}} |

### Wave 0 Test Files (TDD tasks)

<!-- List any test files that must be created BEFORE implementation tasks run. -->
<!-- These are referenced as `<automated>MISSING</automated>` in task verify blocks. -->

| Test File | Created By Task | For Task(s) |
|-----------|----------------|-------------|
| {{test_file_path}} | Task {{N}} | Task {{M}} |

### Automated Verify Commands

<!-- Summary of all `<automated>` commands across tasks. -->
<!-- Executor and verifier use these as the ground-truth test set. -->

```bash
# Per-task verify commands (replicated here for quick reference)
{{command}}
```

### Feedback Latency

<!-- Are any verify commands slow (>30s)? Flag them. -->
<!-- Long-running suites should have a faster smoke-test fallback. -->

- Estimated total verify time: < {{N}} seconds
- Slow commands (>30s): {{none / list}}
