blueBench manual

Checks a frozen lab run manifest and its intended conclusion against deterministic license rules before the experiment ships, and signs a LICENSED / QUESTIONABLE / REFUSED / CANNOT-CERTIFY packet with the smallest evidence set needed to clear each open hold.

What this product is and is not

Is: Experiment preflight gate.

Is not: No instrument control, no LIMS write access, no biological truth claim, and no prediction of an experimental outcome.

Who uses it

Lab and research-integrity reviewers.

Getting started — the local demo

From the product's own repository:

make demo
make verify-demo

This runs entirely offline against synthetic fixtures and exits non-zero on any mismatch. It does not connect to any production data source.

Screen-by-screen walkthrough

Run manifest intake License decision — LICENSED / QUESTIONABLE / REFUSED / CANNOT-CERTIFY with typed holds

blueBench Run license preflight screen: a Licensed verdict for a morphology conclusion, 4 of 5 conditions satisfied and none failed, with a claim-boundary note that the license reflects recorded input capability, not a scientific prediction. — Synthetic demo data
License decision — a Licensed verdict shown here; QUESTIONABLE, REFUSED, and CANNOT-CERTIFY are the same screen's other typed outcomes.

What a receipt proves

A signed receipt proves what blueBench ran and recorded; it does not prove an underlying real-world claim is true. Anyone can check the signature offline with the standalone verifier shipped alongside the product, without installing blueBench itself.

Known gaps, stated plainly

Under active build — see the status page for the measured current state.

FAQ

Does blueBench make the decision for me?

No. No instrument control, no LIMS write access, no biological truth claim, and no prediction of an experimental outcome.

Does blueBench replace the system I already use?

No — it is an overlay. Your existing record system, LIMS, or claims platform stays exactly where it is.