blueRecall manual
Given a defective reagent lot, a stale calibration, or a software defect, traces the dependency graph in a lab run manifest and signs a per-claim verdict — REVOKED, RERUN-REQUIRED, DEGRADED, UNAFFECTED, or CANNOT-CERTIFY — plus the smallest rerun set that restores what's affected.
Is: Reverse impact when an input goes bad.
Is not: No automatic deletion, retraction, notification, or production-system write, and no claim that an unaffected result is scientifically true.
Lab and research-integrity reviewers.
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.

Trigger intake — a defective lot, stale calibration, or defect report registered, with every source file hashed and validated.

Impact verdicts per conclusion, with a rerun-plan cost estimate for the smallest set that needs it.
- Under active build — see the status page.
Does blueRecall make the decision for me?
No. No automatic deletion, retraction, notification, or production-system write, and no claim that an unaffected result is scientifically true.
Does blueRecall replace the system I already use?
No — it is an overlay. Your existing record system, LIMS, or claims platform stays exactly where it is.