BSC Audit Engine · research preview

Turn material into a rigorous audit packet.

Paste a claim or attach a file. This page combines it with the versioned BSC protocol for the language model you choose.

Local by design. Your pasted text and files stay in this browser. There is no account, upload endpoint, analytics script, or third-party library.

Protocol in use

Version
Loading...
SHA-256
Loading...
Verification
Checking local protocol bytes...

One page, three steps

Build your audit request

0 characters. Pasted text is held only in this page's memory.

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.

    3 Choose audit depth

    Verifying the protocol before packet creation.

    Preview the assembled packet

    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.

    1. 1PasteAdd a claim or excerpt.
    2. 2ChooseSelect the audit depth.
    3. 3BuildGenerate a bound packet.
    4. 4AttachSend packet and files together.
    5. 5AuditReceive prioritized findings.

    Read before relying

    A careful packet is not a truth certificate.

    The builder assembles instructions. It does not run the Python checker, verify citations, authenticate evidence, execute theorem provers, or decide 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.