Documentation.
How the instruments are installed, what they ask you for, what comes back, and what a result is not allowed to claim. Written task-first: find the thing you are trying to do, not the feature you are trying to learn.
Nothing has shipped. Checkout is not open, no instrument is available, and no measurement from an instrument these docs describe has been published. Every page here describes intended behaviour and says so at the top. It exists now, before the first customer, because documentation written after launch is documentation written under pressure — and because publishing the intended workflow in advance is what makes it possible to hold the shipped product against it.
- Doc pages
- 9
- Step-by-step procedures
- 3
- Instrument version documented
- NOT YET PUBLISHED
- Support model
- Asynchronous, self-service first
Where to start
Which page to open first depends on the thing you are trying to do.
- Never seen this beforeRead in number order, 1 to 9. The sequence follows a real first run: what arrives, what it asks you for, what comes back, and what the answer is not allowed to claim. Start at Installing an instrument.
- Holding a resultStart at Reading a result(4), which sets the order a panel is meant to be read in. Then When an instrument refuses to answer(5) if a dimension declined to answer, and What a result does not establish(6) before quoting anything to anyone.
- Something went wrongGo straight to Troubleshooting(7) and work down its checks in order.Support and FAQ(8) states what to send and what the support model covers.
Getting started
What arrives, what it asks you for, and which suite answers your question. Nothing has shipped, so these are the specification being built to rather than a walkthrough you can follow today.
Installing an instrument
The three delivery shapes, what each one asks of your machine, and what to have ready before the first run.
Your first measurement
What you provide, what happens to it, and what the run hands back — including the case where the answer is nothing.
Workflows by suite
What each of the seven suites will ask for, what it returns, and the decision it is built to inform.
Reading output
The order a result is meant to be read in, the three different shapes an empty result takes, and the limits that travel with every number an instrument produces.
Reading a result
Read the sample before the number. How the output is laid out, and how to recognise an honest null.
When an instrument refuses to answer
What INSUFFICIENT-n means, why the bar is set before the run, and why a refusal is the feature.
What a result does not establish
Description is not intent, measurement is not prediction, and nothing here is advice. The limits are part of the result.
Getting help
The ordered checks to run when a run does not behave, what to send if none of them explain it, and exactly what the support model will and will not do.
Troubleshooting
Refusals, disagreeing runs, missing dimensions, rejected files — and what to gather before asking for help.
Support and FAQ
The support model — asynchronous, text-first, self-service first — plus the questions asked most often.
Preparing an artifact for an assay
Per-assay export instructions: what file, from where, in what shape, and the one question only you can answer.
Where the docs end
The pages here cover using an instrument. They deliberately do not restate the method. For how a measurement is defined, pre-registered and made recomputable, read the methodology. For the strict sense of a term used in an output, read the glossary. For which instrument answers which question, read the suites or the full instruments index. For what the pricing structure will be when checkout opens, read the pricing model.