Gate the handoff before agreement or adjudication
Check the two returns and key
Nothing is uploaded. Exact imported hashes cover the supplied bytes; reconstructed hashes cover canonical blank packets derived from the parsed returns.
Exact E045 input schemas
The checker accepts only the packet generator’s exact 13-column reviewer header and exact 22-column restricted-key header. It does not guess renamed, reordered, or missing columns.
| Columns 1–7: reconstructed blank | Columns 8–13: completed return | Completion rule |
|---|---|---|
packet_id, target_entity, exact_prompt, answer_text, citation_evidence, engine_surface, run_timestamp | brand_mentioned, brand_cited, actively_recommended, reviewer_confidence, abstention_reason, reviewer_note | All three endpoints are exact and nonblank. Unknown or ineligible requires a reason. Confidence follows the frozen vocabulary; note is optional. |
| Identity and mappings | Evidence and concealed metadata | Eligibility and inclusion |
|---|---|---|
source_response_id, packet_a_id, packet_b_id | target_entity, exact_prompt, answer_text, citation_evidence, original_engine_surface, reviewer_engine_surface, original_run_timestamp, reviewer_run_timestamp, collection_period, comparison_arm, prior_label, expected_outcome, evidence_reference, collector_note | review_eligibility, exclusion_reason, residual_cue_status, residual_cue_note, packet_inclusion |
Method, release posture, and limits
The checker hashes the exact imported bytes. It separately reconstructs each original blank reviewer packet by preserving the parsed row order and first seven fields, clearing only the six return fields, and serializing every field in double quotes with UTF-8 and CRLF. This allows ordinary CSV quoting and line-ending reserialization while making any changed ID, evidence value, row, order, or retained spreadsheet-safety prefix visible through the reconstructed hash.
A passing run requires both reconstructed hashes, the exact restricted-key hash, unique and complete mappings, exact reviewer-visible evidence, completed endpoint fields, valid abstention reasons, the frozen confidence vocabulary, and all process declarations. The joined CSV retains the full key metadata plus both separate return-field sets; it contains no agreement, consensus, accuracy, truth, or adjudication field.
=, +, -, @, ＝, ＋, －, or ＠ receive a disclosed leading horizontal tab only in the joined download. Existing packet and key values are not re-defended. This changes output bytes and is not universal protection across spreadsheet importers.The checker does not upload, store, share, sign, authenticate, correct, overwrite, calculate agreement, score accuracy, vote, adjudicate, certify compliance, or enforce key custody. Hash matches do not prove file authorship, external retention, independent review, successful blinding, label correctness, or fitness for a decision.
Method sources and workflow context
- Rayyan blind-mode documentation places completion of reviewer decisions before unblinding and conflict resolution.
- Potato annotation documentation documents retained annotator responses, assignment controls, and adjudication workflows.
- SciSpace duplicate-screening reconciliation agent illustrates the broader conflict and agreement job that this checker intentionally does not duplicate.
- MDN SubtleCrypto digest documentation describes the browser API used for SHA-256 calculations.
- OWASP CSV Injection guidance explains why ordinary CSV quoting alone does not prevent formula interpretation.
Frequently asked questions
What files does the reviewer return integrity checker require?
It requires completed reviewer-A and reviewer-B CSVs from the Quoted First packet generator, the exact restricted-key CSV, and retained SHA-256 references for both original blank packets and the key. Each input is limited to valid UTF-8, 5 MB, and 5,000 data rows.
Why reconstruct each blank reviewer packet?
Clearing only the six return fields and canonically reserializing the imported values checks whether packet IDs, evidence, rows, order, and retained spreadsheet-safety prefixes still match the original blank-packet hash while allowing intended label entry and ordinary CSV reserialization.
Does a matching hash prove a file is authentic?
No. A match establishes consistency with supplied references and deterministic reconstruction. It does not prove who created or retained a file, whether the references are authentic or out-of-band, or whether the original files were already altered before their hashes were recorded.
What reviewer labels are accepted?
Mention, citation, and active-recommendation fields accept only yes, no, unknown, or ineligible. Unknown or ineligible requires a nonblank abstention reason. Confidence follows a coordinator-frozen case-sensitive vocabulary of at most twelve values; blank is allowed only when predeclared.
Does this checker calculate agreement or adjudicate labels?
No. It preserves both returned label sets and produces a pre-adjudication join only after integrity checks pass. It computes no agreement statistic, accuracy score, consensus, majority vote, correction, or final label.
Where are the reviewer files sent?
Nowhere by this page. Parsing, exact hashing, reconstruction, mapping checks, preview, and downloads happen locally in the current browser tab. Reloading clears the imported files and results.
Measure agreement without overwriting either reviewer
Use the preserved pre-adjudication label sets for endpoint-specific agreement QA. Keep any later resolution separate from the original independent record.