# Final evidence check

Map spec promises to valid observed proof.

## Acceptance

For each AC/REQ/scenario/key link, exact `devrites-proof-runner` maps immutable
results and exact `devrites-spec-reviewer` checks implementation and proof
against its meaning. Bug fixes require original-symptom proof; self-report,
inspection alone, and generic "tests pass" do not count.

Apply [[`testing.md`](../../devrites-lib/reference/standards/testing.md)'s positive, discriminating proof](../../devrites-lib/reference/standards/testing.md#positive-discriminating-proof),
including invalid-result exclusions and static/textual criterion boundaries.
Unproven behavior: NO-GO.

## Cross-check

Require built slices, resolved or accepted findings, no drift/open validating
question, required UI/boundary proof, and an exact doubt verdict per stood decision.
Reconcile the final diff with the spec applicability map. Every triggered topology,
data, integration, security, and delivery owner needs its relevant observed failure/
recovery evidence or an evidence-backed dismissal; a generic green suite cannot close it.

## Candidate binding and test integrity

Run `devrites-engine check candidate <slug>` and require its digest to match the
single evidence/review bindings and browser binding when present. Diff tests,
dispatch exact `devrites-test-analyst`; apply
[evidence validity](../../devrites-lib/reference/candidate-integrity.md#evidence-validity)
to approved proof, then require unchanged digest/sources. Deleted/skipped/focused/
weakened/tautological tests are Critical.

After recording verdicts in `seal.md`, run:

```bash
devrites-engine check seal "<slug>"
```

This checks structure and exact candidate bindings, never acceptance, test
quality, doubt, or review. Apply [[`testing.md`](../../devrites-lib/reference/standards/testing.md)'s safe perturbation](../../devrites-lib/reference/standards/testing.md#safe-perturbation)
for its mandatory critical/regression cases and any additional project/test-plan requirement.