Evidence-First Execution designed
Evidence-first execution means every change is proven relative to a baseline and completed with direct proof of the intended outcome.
Minimum Pattern
- Establish a relevant baseline.
- Make the smallest verifiable change.
- Predict the expected outcome.
- Re-run the scoped check.
- Record proof, review, and residual risk.
Compiles, screenshots, and "looks right" can be useful signals, but they are not enough when the change affects behavior, security, release, or contracts.
Fairway Provider Session Sequence
Evidence Quality Bar
| Evidence type | Required contents |
|---|---|
| Test or gate | Exact command, result, artifact path, and relevant source SHA |
| CI/deploy monitor | Pipeline or deploy URL, expected window, terminal result, failed jobs or findings |
| UAT/smoke | Scenario matrix, environment, pass/fail classification, and follow-up task ids |
| Review | Reviewer domain, verdict, scope reviewed, and reason |