Profile 03 · Sequencing and diagnostic laboratories
Your client must be able to show, months later, that the result is the one that came out of the computation.
A laboratory delivers files. What sets a delivery apart is that the researcher can defend it to a reviewer without calling you back.
What cannot be solved today
The delivery ends in a file, and that is where the client's problem begins.
The researcher receives FASTQ or VCF and has to produce, on their own, the traceability they will be asked for.
Every client asks about different versions.
Answering case by case consumes commercial and technical time that is never billed.
Two deliveries from the same laboratory are not comparable.
Parameters changed between one run and the next and nobody wrote it down.
What we deliver
A version manifest attached to the delivery
The client receives the file and, with it, what it was produced with. It stops being a support query and becomes part of the product.
A documented intake workflow
What is accepted, what is rejected and why. The criterion is written once and applied every time.
An evidence layer under your brand or alongside it
Scope and attribution are defined by contract before we start.
Available Computed today on public microbiome data. In genomics, the public demonstration uses synthetic annotation; real sources are agreed by contract.
The proof, checkable now
52
public files with SHA-256
The manifest lists the downloads in this frozen example. Each run produces its own artifacts, eligibility states and provenance.
- Dataset
- nexalel-review-challenge.1729
- Method version
- Snakemake · microbiome-counts-analysis 1.0.0
- Run identifier
- Frozen example · verifiable scientific fingerprint
- Artifact hash
- c6e94ce77eca7a96900596a7b8db1d87ce3272a1ee56f7417f6471c4057f9331
- Seed
- 1729
The check runs in your browser and confirms file integrity. It does not replace scientific review or a fresh run.
What held up
A diversity signal holds under the documented depth check.
What did not hold up
Of the two significant contrasts, neither survived the sensitivity test. We publish that too.
We publish both. A method that only shows its successes cannot be evaluated.
Download the synthetic tables and test the analysis ↓ · 0.01 MB · No account, no form and no sales call.
Questions your procurement team will ask
Does this compete with our pipeline?
No. We work on your output and add the provenance layer that each client currently builds on their own.
Can we offer it to our clients?
That is a contract conversation. Scope, attribution and price are agreed in writing.
Which formats do you accept?
16S amplicon for microbiome and VCF for genomics. Any other format is assessed before we commit.
Is there an API integration?
Not available today, and not promised. What exists is the exchange of artifacts with a manifest.
What does your next study have to demonstrate?
We first agree on the question, the assay, the data rights and the deliverable. Then we decide whether working together makes sense.