Verification
How Spectrace verifies a pull request against the requirement it claims to implement, and how to read the result.
Verification is where a requirement meets the code. These pages explain what triggers a run and what is compared, how a pull request is linked to a requirement, how to read the comment and the check run, how to use the check run as a merge gate, and what the spec-drift note means.
- How PR verification worksWhat triggers a verification, what Spectrace compares, the five per-criterion verdicts, and where the result lands.
- Linking a PR to a requirementHow Spectrace decides which requirement a pull request is verified against, how to write a reference that resolves, and what to do when it does not.
- Reading a verification resultThe three shapes a verification comment takes, what each line means, where the full breakdown lives, and what to do next.
- Check runs and branch protectionHow the Spectrace verification check run maps verdicts to success, neutral, and failure, and how to make it a required check.
- Spec driftWhat the drift note in a verification comment means, when it appears, and what to do about it.