Evidence Locker: SHA-256 test evidence for every failure.
The Evidence Locker is the Nexus StudioQA screen where every result is filed. A failed test leaves a forensic report, metadata, a raw log and a screenshot, plus a video for a real failure. Sealing is opt-in: it hashes each file with SHA-256 and chains the record to the one before, so a check names the first record that changed.
By the Nexus StudioQA team, Verdict System LLC.
Last updated: .
What a failed test leaves behind
| File | What it holds |
|---|---|
| report.md | The forensic report in Markdown, readable without the Studio. |
| metadata.json | Machine-readable fields about the run. It is also the file the chain of custody seals: a folder with a metadata.json is a record. |
| raw-data.json | Console lines, network errors, security issues, page errors and performance samples. |
| screenshot.png | One viewport screenshot of the final frame. |
| video.webm | The session. A real failure keeps it: BREACHED, BREACHED_FLAKY and CHAOS_BREACHED by default, TIMEOUT and BLOCKED when you turn them on in Settings. |
Sealing and verifying
Sealing starts with the first Real bug or False alarm call in the Studio, or with nexus verify --seal. Records go into one append-only ledger, evidence/chain-of-custody/ledger.jsonl, using only Node.js's built-in crypto.
| State | What it means | Exit code |
|---|---|---|
| UNVERIFIED | No ledger yet, so nothing can be proven. Never a silent OK. | 2 |
| VERIFIED | Every sealed record and file matches its hash. | 0 |
| TAMPER DETECTED | A file or a ledger line changed after sealing; the first broken record is named. | 1 |
| PURGED | A sealed folder was removed on purpose, and the ledger says who removed it and when. | n/a |
Where it lives and how it stays bounded
On your disk
Evidence is written to the machine that ran the test. The one connection the product makes on its own is the license check, and it carries no test data.
One total budget
NEXUS_EVIDENCE_MAX_GB, 20 GB by default, bounds all evidence together. The newest run of each test and browser and the chain of custody ledger are never removed.
Cleanup leaves a trace
Before a sealed folder is removed, a PURGE entry goes into the ledger, so the check reports PURGED, not tampered. If the ledger cannot record it, the folder stays.
What sealing does not prove
Sealing proves the files did not change after sealing, not that they were right before. The ledger sits on the same disk as the evidence, so keep the tip hash that sealing prints somewhere else, such as a ticket or a release note. Chain of custody for test evidence shows real nexus verify output and its limits. Verify a download is a different check: the installer's code signature and SHA-256.
Common questions
What does the Evidence Locker keep when a test fails?
A folder with the forensic report, metadata, the raw log and a screenshot of the final frame, plus the video for a real failure. With your AI connected, an AI analysis is added to the report.
Is SHA-256 sealing automatic?
No, it is opt-in. It starts with the first Real bug or False alarm call in the Studio, or with nexus verify --seal. With no ledger, the check reports UNVERIFIED and exits 2.
Does sealing prove the evidence was correct?
No. A record sealed after an edit seals the edit. Only sealed records are covered; evidence written before the first seal stays UNVERIFIED until you seal it.
Does my evidence leave my machines?
No, not on its own. Anything you connect, such as Jira or Slack, is reached straight from your machine, never through us. Only a screenshot is attached to Jira unless you opt in to more.
Run it on your own machine.
Try every feature free, on your own machines. No card needed.