Evidence Standards
File & Hash Standards
The required structure for every Word Detail File, Video Evidence, and SHA256 seal produced after a comparison.
8Required File Sections
1Hash Per Comparison
Required Structure
Word Detail File
| # | Required Section |
|---|---|
| 1 | Comparison ID, start date/time → publish date/time |
| 2 | The original question |
| 3 | Blind Spot List (3 independent versions + merged version) |
| 4 | The complete Phase 1 and Phase 2 logs |
| 5 | 3 individual Review scores + the average, across the 5 criteria |
| 6 | Post-Comparison Citation Audit |
| 7 | Role Rotation Log (AI – role – account) |
| 8 | SHA256 (computed after the file is fully finalized) |
SHA256 is never computed early and then edited afterward — this avoids a hash-then-edit-then-rehash loop that would make the hash meaningless.
Requirements
Video Evidence
1
The Arena Master narrates the entire comparison.
2
States the Comparison ID, and summarizes the question, the outcome, and the scores.
3
Production quality is not the priority — authenticity and completeness matter more than polish.
Computation Rule
SHA256
1
Computed on the final, fully completed Word Detail File, only after every piece of content is locked.
2
The hash is published alongside the original file so anyone can independently verify it.
Standard
A File Without A Hash Is Not Evidence
Every comparison record on BigAIArena follows this same eight-part structure, sealed by a single SHA256 computed only once the file is final. See Data Repository for where these files are stored and retrieved.