So a confession first, I spent two months building a tool and only now thought to ask whether anyone needs it in bioinformatics. Classic engineer right? Measure never, cut twice. Background. I come from regulated software industry, where traceability is not a hobby, it is a compliance requirement. Every change points to a requirement, every requirement points to a test, and when a bug is found you must say exactly which product type it reached. Auditors visit. They do not laugh istg! So I assumed bioinformatics was the same, and built github.com/QuietFlare/clew. It reads the Nextflow lineage store and answers for ex: these two samples were swapped at intake, what did they touch, and what do I do with each output, and can seal that answer as a report. Now the stupid question. Is that a real need? When a reference input or container turns out faulty after a run, does anyone in clinical or regulated settings have to produce an impact record an auditor would ask and accept? Or does everyone just type -resume, say a small prayer, and move on? I would honestly like to know which world I built this for. Thread in Slack conversation