Barcode autopsy: weak signal and unsafe rescue

• Category: Report zoo

• Assay type: inline_barcode

• Evidence level: Documented example

• Dataset: SRP009896/SRR391079 barcode autopsy fixture

• Condition shown: A review-status run with low-confidence offset evidence, low assignment rate, high ambiguity, and unsafe one-edit correction.

• Primary report: docs/evidence-gallery/snapshots/barcode_autopsy/report.html

What This Shows

• DotMatch can turn a suspicious barcode run into a readable report with findings, next actions, and command provenance.

• The report keeps ambiguous and unmatched evidence instead of silently assigning it.

• Unsafe one-edit correction is surfaced as a report finding.

What It Does Not Show

• The review status is intentional and should not be interpreted as a production-ready barcode assignment.

• Users must correct the assay specification or barcode design before trusting rescued reads.

Comparator And Validation

Comparator semantics: This is a diagnostic barcode autopsy run, not a broad comparator benchmark. It records the configured fixed-window barcode semantics and native audit/inspect-unmatched commands.

Validation: The report is generated from committed autopsy outputs and checked by barcode validation fixtures.

Report Examples

• Barcode autopsy HTML report (html)

• Barcode autopsy Markdown report (markdown)

• Findings table (tsv)

Raw Artifacts

• docs/evidence-gallery/snapshots/barcode_autopsy/findings.tsv

• docs/evidence-gallery/snapshots/barcode_autopsy/offset_scan.tsv

• docs/evidence-gallery/snapshots/barcode_autopsy/collision_graph.tsv

• docs/evidence-gallery/snapshots/barcode_autopsy/correction_safety.tsv

• docs/evidence-gallery/snapshots/barcode_autopsy/top_unmatched.tsv

• docs/evidence-gallery/snapshots/barcode_autopsy/provenance.json

Reproduce Or Check

• make barcode-autopsy-demo

• make barcode-validation-ready