Sample release evidence audit
This is the report Tracer writes about a release, run on Tracer itself. Dataset: Tracer's own TC backlog, fetched 2026-10-09T18:24:44Z; CI run 37964978955 at 238c56d5b58e48c103db28288d207703e9be3cbf.
The backlog is Tracer's product work only: the 227 Jira issues whose parent Epic sits under one of the five buyer-outcome Initiatives (TC-205, TC-206, TC-207, TC-208, TC-209), from the query project = TC AND created >= "2026-09-14" AND issuetype in (Task, Bug, Story) AND parent in (TC-210,TC-211,TC-212,TC-213,TC-214,TC-215,TC-216,TC-248,TC-250,TC-256,TC-268,TC-272,TC-273,TC-333,TC-393,TC-401,TC-444,TC-807,TC-809,TC-822,TC-826,TC-865) ORDER BY key: 190 Tasks and Stories read as requirements and 37 Bugs read as defects. Issue titles are not published; this sample shows each record's key, type and status. The test evidence is the 3947 test cases in the JUnit report of the ci.yml run 37964978955 on vorthruna/tracer-next. Every number below was computed from those two files by released Tracer code when this site was built, as of 2026-10-09T18:24:44Z.
From Jira, Tracer kept only these fields: key, issuetype.name, status.name, priority.name, fixVersions[].name, issuelinks[].type and linked key, updated. It kept no descriptions, no comments, no people and no custom fields. Your own audit keeps the same list.
1. Verdict
Not ready to sign off: 22 of 190 requirements have a passing test and no failing one, and 168 have no test result showing they work.
2. Requirements by what the evidence shows
| Verified | Falsified | Unknown | Total |
|---|---|---|---|
| 22 | 0 | 168 | 190 |
Verified means a fresh CI test that names the requirement's key passed and none failed. Falsified means one failed. Unknown means no fresh test shows either. The three counts add up to the total; Tracer does not turn them into a percentage.
The 22 verified requirements:
| Key | Type | Status | Why it is verified |
|---|---|---|---|
| TC-226 | Task | Deployed | 6 CI tests name it; 6 fresh runs passed and none failed. |
| TC-228 | Task | Deployed | 5 CI tests name it; 5 fresh runs passed and none failed. |
| TC-421 | Task | Deployed | 1 CI test names it; 1 fresh run passed and none failed. |
| TC-427 | Task | Deployed | 3 CI tests name it; 3 fresh runs passed and none failed. |
| TC-664 | Task | Deployed | 4 CI tests name it; 4 fresh runs passed and none failed. |
| TC-669 | Task | Deployed | 2 CI tests name it; 2 fresh runs passed and none failed. |
| TC-808 | Task | Deployed | 3 CI tests name it; 3 fresh runs passed and none failed. |
| TC-816 | Task | Deployed | 6 CI tests name it; 6 fresh runs passed and none failed. |
| TC-817 | Task | Deployed | 23 CI tests name it; 23 fresh runs passed and none failed. |
| TC-818 | Task | Deployed | 7 CI tests name it; 7 fresh runs passed and none failed. |
| TC-819 | Task | Deployed | 24 CI tests name it; 24 fresh runs passed and none failed. |
| TC-820 | Task | Deployed | 18 CI tests name it; 18 fresh runs passed and none failed. |
| TC-957 | Task | Deployed | 45 CI tests name it; 45 fresh runs passed and none failed. |
| TC-1093 | Task | Deployed | 6 CI tests name it; 6 fresh runs passed and none failed. |
| TC-1101 | Task | Deployed | 43 CI tests name it; 43 fresh runs passed and none failed. |
| TC-1116 | Task | In Progress | 5 CI tests name it; 5 fresh runs passed and none failed. |
| TC-1170 | Task | Deployed | 9 CI tests name it; 9 fresh runs passed and none failed. |
| TC-1171 | Task | Deployed | 13 CI tests name it; 13 fresh runs passed and none failed. |
| TC-1177 | Task | Deployed | 4 CI tests name it; 4 fresh runs passed and none failed. |
| TC-1194 | Task | Deployed | 26 CI tests name it; 26 fresh runs passed and none failed. |
| TC-1195 | Task | Deployed | 1 CI test names it; 1 fresh run passed and none failed. |
| TC-1198 | Task | Tested | 1 CI test names it; 1 fresh run passed and none failed. |
3. Requirements Tracer cannot call either way
168 requirements, each with the reason.
| Key | Type | Status | Why it is unknown |
|---|---|---|---|
| TC-217 | Task | Deployed | No CI test names it. |
| TC-218 | Task | New | No CI test names it. |
| TC-219 | Task | New | No CI test names it. |
| TC-220 | Task | Deployed | No CI test names it. |
| TC-221 | Task | Deployed | No CI test names it. |
| TC-222 | Task | Tested | No CI test names it. |
| TC-223 | Task | Backlog | No CI test names it. |
| TC-224 | Task | Deployed | No CI test names it. |
| TC-225 | Task | Backlog | No CI test names it. |
| TC-227 | Task | Deployed | No CI test names it. |
| TC-229 | Task | Backlog | No CI test names it. |
| TC-230 | Task | Backlog | No CI test names it. |
| TC-231 | Task | Done | No CI test names it. |
| TC-232 | Task | Deployed | No CI test names it. |
| TC-249 | Task | Deployed | No CI test names it. |
| TC-251 | Task | Done | No CI test names it. |
| TC-254 | Task | New | No CI test names it. |
| TC-255 | Task | New | No CI test names it. |
| TC-257 | Task | Backlog | No CI test names it. |
| TC-258 | Task | New | No CI test names it. |
| TC-259 | Task | New | No CI test names it. |
| TC-260 | Task | Deployed | No CI test names it. |
| TC-261 | Task | New | No CI test names it. |
| TC-262 | Task | New | No CI test names it. |
| TC-263 | Task | New | No CI test names it. |
| TC-264 | Task | New | No CI test names it. |
| TC-265 | Task | Deployed | No CI test names it. |
| TC-269 | Task | Backlog | No CI test names it. |
| TC-270 | Task | Backlog | No CI test names it. |
| TC-271 | Task | Backlog | No CI test names it. |
| TC-274 | Task | Deployed | No CI test names it. |
| TC-275 | Task | New | No CI test names it. |
| TC-276 | Task | New | No CI test names it. |
| TC-277 | Task | Deployed | No CI test names it. |
| TC-278 | Task | New | No CI test names it. |
| TC-279 | Task | Deployed | No CI test names it. |
| TC-280 | Task | Deployed | No CI test names it. |
| TC-281 | Task | Deployed | No CI test names it. |
| TC-326 | Task | Deployed | No CI test names it. |
| TC-328 | Task | New | No CI test names it. |
| TC-329 | Task | Backlog | No CI test names it. |
| TC-330 | Task | Deployed | No CI test names it. |
| TC-331 | Task | Backlog | No CI test names it. |
| TC-332 | Task | Deployed | No CI test names it. |
| TC-395 | Task | New | No CI test names it. |
| TC-399 | Task | New | No CI test names it. |
| TC-402 | Task | Done | No CI test names it. |
| TC-403 | Task | Backlog | No CI test names it. |
| TC-404 | Task | Backlog | No CI test names it. |
| TC-405 | Task | Backlog | No CI test names it. |
| TC-407 | Task | Deployed | No CI test names it. |
| TC-409 | Task | New | No CI test names it. |
| TC-410 | Task | New | No CI test names it. |
| TC-411 | Task | New | No CI test names it. |
| TC-413 | Task | New | No CI test names it. |
| TC-415 | Task | Deployed | No CI test names it. |
| TC-417 | Task | Deployed | No CI test names it. |
| TC-419 | Task | Deployed | No CI test names it. |
| TC-420 | Task | Backlog | No CI test names it. |
| TC-423 | Task | Deployed | No CI test names it. |
| TC-424 | Task | Deployed | No CI test names it. |
| TC-428 | Task | Deployed | No CI test names it. |
| TC-430 | Task | Deployed | No CI test names it. |
| TC-456 | Task | Deployed | No CI test names it. |
| TC-460 | Task | Done | No CI test names it. |
| TC-461 | Task | New | No CI test names it. |
| TC-534 | Task | New | No CI test names it. |
| TC-535 | Task | New | No CI test names it. |
| TC-566 | Task | Deployed | No CI test names it. |
| TC-567 | Task | Deployed | No CI test names it. |
| TC-594 | Task | Deployed | No CI test names it. |
| TC-657 | Task | Backlog | No CI test names it. |
| TC-665 | Task | Deployed | No CI test names it. |
| TC-666 | Task | New | No CI test names it. |
| TC-667 | Task | New | No CI test names it. |
| TC-668 | Task | Deployed | No CI test names it. |
| TC-706 | Task | New | No CI test names it. |
| TC-707 | Task | New | No CI test names it. |
| TC-708 | Task | Tested | No CI test names it. |
| TC-717 | Task | New | No CI test names it. |
| TC-718 | Task | New | No CI test names it. |
| TC-719 | Task | New | No CI test names it. |
| TC-720 | Task | Deployed | No CI test names it. |
| TC-721 | Task | New | No CI test names it. |
| TC-722 | Task | New | No CI test names it. |
| TC-724 | Task | Backlog | No CI test names it. |
| TC-725 | Task | New | No CI test names it. |
| TC-726 | Task | Backlog | No CI test names it. |
| TC-734 | Task | Backlog | No CI test names it. |
| TC-737 | Task | Backlog | No CI test names it. |
| TC-739 | Task | Backlog | No CI test names it. |
| TC-740 | Task | New | No CI test names it. |
| TC-741 | Task | Backlog | No CI test names it. |
| TC-742 | Task | Backlog | No CI test names it. |
| TC-743 | Task | Backlog | No CI test names it. |
| TC-744 | Task | Backlog | No CI test names it. |
| TC-745 | Task | Backlog | No CI test names it. |
| TC-746 | Task | Backlog | No CI test names it. |
| TC-747 | Task | Backlog | No CI test names it. |
| TC-748 | Task | Backlog | No CI test names it. |
| TC-749 | Task | Backlog | No CI test names it. |
| TC-750 | Task | Backlog | No CI test names it. |
| TC-751 | Task | Backlog | No CI test names it. |
| TC-752 | Task | Backlog | No CI test names it. |
| TC-753 | Task | Backlog | No CI test names it. |
| TC-754 | Task | New | No CI test names it. |
| TC-758 | Task | New | No CI test names it. |
| TC-759 | Task | Backlog | No CI test names it. |
| TC-761 | Task | New | No CI test names it. |
| TC-762 | Task | New | No CI test names it. |
| TC-764 | Task | New | No CI test names it. |
| TC-765 | Task | New | No CI test names it. |
| TC-766 | Task | New | No CI test names it. |
| TC-767 | Task | New | No CI test names it. |
| TC-768 | Task | New | No CI test names it. |
| TC-769 | Task | New | No CI test names it. |
| TC-770 | Task | New | No CI test names it. |
| TC-782 | Task | New | No CI test names it. |
| TC-810 | Task | Backlog | No CI test names it. |
| TC-811 | Task | Backlog | No CI test names it. |
| TC-812 | Task | Backlog | No CI test names it. |
| TC-835 | Task | Deployed | No CI test names it. |
| TC-847 | Task | Deployed | No CI test names it. |
| TC-848 | Task | New | No CI test names it. |
| TC-862 | Task | Backlog | No CI test names it. |
| TC-872 | Task | Backlog | No CI test names it. |
| TC-873 | Task | Backlog | No CI test names it. |
| TC-874 | Task | Backlog | No CI test names it. |
| TC-875 | Task | Backlog | No CI test names it. |
| TC-876 | Task | Backlog | No CI test names it. |
| TC-887 | Task | Backlog | No CI test names it. |
| TC-888 | Task | Backlog | No CI test names it. |
| TC-889 | Task | Backlog | No CI test names it. |
| TC-897 | Task | Backlog | No CI test names it. |
| TC-898 | Task | Deployed | No CI test names it. |
| TC-899 | Task | Backlog | No CI test names it. |
| TC-900 | Task | Backlog | No CI test names it. |
| TC-901 | Task | Deployed | No CI test names it. |
| TC-902 | Task | Deployed | No CI test names it. |
| TC-903 | Task | New | No CI test names it. |
| TC-904 | Task | Deployed | No CI test names it. |
| TC-906 | Task | New | No CI test names it. |
| TC-907 | Task | Deployed | No CI test names it. |
| TC-908 | Task | New | No CI test names it. |
| TC-933 | Task | Done | No CI test names it. |
| TC-937 | Task | New | No CI test names it. |
| TC-989 | Task | New | No CI test names it. |
| TC-992 | Task | Deployed | No CI test names it. |
| TC-996 | Task | Backlog | No CI test names it. |
| TC-999 | Task | New | No CI test names it. |
| TC-1039 | Task | Deployed | No CI test names it. |
| TC-1043 | Task | Deployed | No CI test names it. |
| TC-1044 | Task | Deployed | No CI test names it. |
| TC-1065 | Task | Deployed | No CI test names it. |
| TC-1086 | Task | Backlog | No CI test names it. |
| TC-1087 | Task | Backlog | No CI test names it. |
| TC-1088 | Task | Backlog | No CI test names it. |
| TC-1089 | Task | Backlog | No CI test names it. |
| TC-1094 | Task | Backlog | No CI test names it. |
| TC-1095 | Task | Backlog | No CI test names it. |
| TC-1106 | Task | Deployed | No CI test names it. |
| TC-1107 | Task | Deployed | No CI test names it. |
| TC-1172 | Task | Done | No CI test names it. |
| TC-1178 | Task | Deployed | No CI test names it. |
| TC-1183 | Task | New | No CI test names it. |
| TC-1200 | Task | In Progress | No CI test names it. |
| TC-1201 | Task | In Progress | No CI test names it. |
| TC-1202 | Task | New | No CI test names it. |
4. Records missing a field a decision needs
None. A release status needs a priority on every requirement and a severity on every defect, and Tracer reads a Bug's Jira priority as its severity. Every record here carries one.
5. Requirements with no test, and tests linked to nothing
| Requirements no CI test names | CI tests naming a requirement | CI tests naming no requirement in this backlog |
|---|---|---|
| 168 | 254 | 3675 |
A test names a requirement when its name carries the requirement's key. A test that names nothing may still be a good test; it just cannot count as evidence for any requirement.
6. Stale and unversioned evidence
| Test runs read | Stale (older than 30 days or superseded) | Unversioned (no code revision) | Skipped or inconclusive | Refused |
|---|---|---|---|---|
| 3929 | 8 | 0 | 2 | 18 |
A stale run never counts as a pass. A superseded run is an earlier result for a test that ran again later. A refused test case had a name longer than 256 characters or one matching a personal-data pattern; it is counted here and not read.
7. How to check the signature
A verdict Tracer issues for your organization carries an Ed25519 signature over its canonical JSON form (RFC 8785). To check one without asking Tracer:
- Fetch the public key set from
/.well-known/tracer-verdict-key. - Remove the
signaturemember from the verdict and canonicalize the rest. - Verify the signature against those bytes with the published key. Any changed field, including the disclosure text, fails the check.
This sample is generated when the site is built, so it is not signed. Its evidence hash is c2114514e7e31f7e7efcf2afc1340ee98046fd5aec78b208ba07d780b0669687 under query version verdict.v1.
8. What this report does not claim
- It does not say the software works or does not work. It says what the records show.
- It gives no quality score and no percentage.
- It does not fill a missing field or invent a test result. A gap is reported as a gap.
- It does not read source code. It reads the delivery records it is given.
- It does not judge whether a test that names a requirement actually checks it.
9. Want this for your release?
Want this for your release? Create a free account and run Tracer on your own records, or read how a pilot works.