# Validation Evidence Template

> Write this file after completing each packet.
> File location: `.harness/<stream>/validation/<xx-NN>-validation.md`
> Commit it in the same commit as the packet code.

---

# [XX-NN] Validation Evidence
**Date:** YYYY-MM-DD
**Agent:** [model name, e.g. claude-sonnet-4.6]
**Stream:** [stream name]
**Packet:** [XX-NN — Packet Name]

## Test Counts
| Metric | Value |
|--------|-------|
| Tests before packet | NNNN |
| Tests after packet | NNNN |
| New tests added | NN |
| TypeScript errors in new files | 0 |

## Known-Answer Tests
<!-- For each known-answer test defined in the execution board: -->
- [x] [Description] (Source: [URL]): PASS
- [x] [Description] (Source: [URL]): PASS

## Acceptance Criteria
<!-- Tick each criterion from the execution board: -->
- [x] [Criterion]: ✅
- [x] Full test suite green: ✅ (NNNN passing)
- [x] TypeScript clean: ✅

## Documentation Check
<!-- For any user-facing feature change: -->
- [ ] Is this change user-facing? (new UI, new tab, new workflow, changed behavior)
  - If YES: which doc was updated? ___________________________
  - If NO: N/A (internal service / refactor / test only)

**Doc files updated** (list any changed):
- `docs/product/...` — [description]
- `packages/fintrove-app/docs/...` — [description]

If no docs needed: briefly explain why: ___________________________

## Files Created
- `src/...` — [N lines, brief description]
- `src/.../__tests__/...` — [N lines, N tests]

## Commit
`[hash]` — [commit message first line]

## Notes
[Implementation decisions, deviations from plan, lessons learned, gotchas]