Paste a claim or attach a file. This page combines it with the versioned BSC protocol for the language model you choose.
Browser-local page code. This page does not transmit target material or intentionally persist it. There is no account, upload endpoint, analytics script, or third-party library. Browser, operating-system, extension, clipboard, and downloaded-file behavior remains outside this page's control.
Protocol in use
Version
Loading...
SHA-256
Loading...
Verification
Checking local protocol bytes...
One page, three steps
Build your audit request
0 characters. Page code does not transmit or intentionally persist this text; browser and operating-system features remain outside its control.
Small text files are embedded locally. PDFs, images, office files, and large files remain companion attachments; the packet records their names, sizes, and local SHA-256 when feasible.
Verifying the protocol before packet creation.
Preview the assembled packet
Local consistency inspection
Audit Return Desk
Bring back a structured audit_return.json and the files it declares. The Desk checks strict JSON, version bindings, source and evidence references, fatal-gate projections, execution disclosures, and local SHA-256 matches.
Consistency is not truth. A consistent result is not proof, citation verification, checker execution, scientific correctness, admissibility, or deployment approval.
Strict parsing rejects duplicate keys, trailing data, non-object JSON, and UTF-8 input above 8 MiB. Page code does not transmit or intentionally persist this text.
Loading a JSON file replaces the pasted return in this page. This page code does not upload it.
The Desk hashes up to 32 readable files locally, at most 64 MiB per file and 256 MiB total, then matches exact filenames and SHA-256 values. Larger or additional declared artifacts remain review-needed. Browser file paths are never collected.
Add a versioned audit return to begin.
Downloaded inspection JSON contains no attached file bytes, but may contain filenames, identifiers, and SHA-256 values. Hashes do not anonymize private material.
Inspection result
Twenty-second walkthrough
From claim to structured audit
The demonstration highlights paste, choose depth, build, attach, and audit in sequence. All steps are also listed as static text.
1PasteAdd a claim or excerpt.
2ChooseSelect the audit depth.
3BuildGenerate a bound packet.
4AttachSend packet and files together.
5AuditReceive prioritized findings.
Read before relying
A careful packet is not a truth certificate.
The builder assembles instructions. The Return Desk performs local structural and hash-consistency checks. Neither runs the BSC Python checker, verifies citation meaning, authenticates evidence, executes theorem provers, or decides whether a scientific theory is true.
Do not upload secrets, identifying records, controlled information, or material you are not allowed to share. Prefer a local approved workflow for sensitive targets.