Rigorous Validation

Intent

• Ship only when behavior is proven, not assumed.
• Treat tests, QA scripts, linters, and on-chain/off-chain simulations as first-class deliverables.
• Capture evidence so reviewers can verify quickly.

Inputs

1. Canonical test commands (unit, integration, e2e, contract sims, UI snapshots).
2. Acceptance criteria plus measurable signals (logs, screenshots, transaction hashes).
3. Migrations/seed data steps required to exercise the change locally.