Quality gates and traceability
Quality gates help decide whether a product state is ready to ship. A gate verdict is computed from requirement coverage, test results, component risk, freshness, and production issues when available.
Scopes
Quality gates can evaluate:
| Scope | What it means |
|---|---|
| Main | Current canonical product repository |
| Branch | A merge-preview projection of a branch |
| Release | A specific release version |
Verdicts
Verdict states include:
- Pass: the gate is clear.
- Blocked: at least one hard gate failed.
- Risk accepted: a soft signal was explicitly accepted.
Some builds may expose risk acceptance only for release scopes.
Component breakdown
Verdicts are grouped by component. Component results can include:
- Coverage failures.
- Pass-rate failures.
- Residual risk.
- Open production issues.
- Fix hints.
Use the component breakdown to decide whether the next action is to add tests, fix failures, accept risk, or investigate production issues.
Traceability matrix
Traceability groups requirements by component and shows related test cases. Requirement coverage values include:
verified: linked tests support the requirement.not_run: linked tests exist but execution state is missing or stale.no_test: no linked test coverage exists.
CLI gate checks
Check current main:
tiden gate check --product-id <product-id>
Check a release:
tiden gate check --product-id <product-id> --release <release-id>
The CLI exits non-zero when a verdict is blocked or needs pending risk review.