Use cases
What teams do with Operon.
Each example follows one question from first lookup to a result your team can stand behind: grounded in curated knowledge graphs, with a decision record behind it.
Talk to UsMicrobiome therapeutics teams
Choosing live-biotherapeutic candidates
Which commensal genera are depleted in this disease, what do they produce, and which are worth taking forward?
Translational and discovery scientists
Explaining a microbiome signal
Our cohort shows this genus dropping. What could the mechanism be?
Teams with their own 16S or metabolomics data
Putting your own study in context
Where do our results agree with the published evidence, and where do they not?
R&D leads and portfolio committees
A go/no-go your leadership can audit
Should we move this indication forward, and can we show why later?
Teams handing results to a partner, a diligence team or a regulator
Reproducing an analysis for a partner or regulator
Can someone outside our team check how this result was produced?
Method owners licensing a method, and the teams that want to use itIn development
Running a partner's method without seeing inside it
Can we use their method on our data without either side exposing what it holds?
Use case 1
Choosing live-biotherapeutic candidates
For microbiome therapeutics teams.
“Which commensal genera are depleted in this disease, what do they produce, and which are worth taking forward?”
You leave with
- —A ranked shortlist with the evidence behind each candidate
- —The open questions worth an experiment
What the record shows
- —Which graph facts and papers each ranking rests on
- —Who approved the shortlist, and when
Illustrative workflow, not a product screenshot
AskWhich commensal genera are depleted in this disease, what do they produce, and which are worth taking forward?
GroundThe disease's microbiome signature in MicroMap: direction, study counts, sources
ReasonWhat each genus produces, and the paths to host targets
ReadEvidence for and against each candidate, and known confounders
CheckA review pass before the shortlist is trusted
RecordReviewer-approved shortlist → your Company Graph
Use case 2
Explaining a microbiome signal
For translational and discovery scientists.
“Our cohort shows this genus dropping. What could the mechanism be?”
You leave with
- —Two or three mechanistic hypotheses, ranked by evidence
- —The experiment that would tell them apart
What the record shows
- —Every path, and the source of each link in it
- —Which hypotheses were kept, and which were set aside
Illustrative workflow, not a product screenshot
AskOur cohort shows this genus dropping. What could the mechanism be?
GroundThe genus and the diseases it is linked to
ReasonMechanistic paths from the microbe through metabolites to host proteins and pathways
ReadStudies that support each path, and those that conflict
CheckA review pass before a hypothesis is trusted
RecordEach hypothesis kept with its evidence
Use case 3
Putting your own study in context
For teams with their own 16S or metabolomics data.
“Where do our results agree with the published evidence, and where do they not?”
You leave with
- —A map of agreements, conflicts and findings that look new
- —Your data linked to the published evidence, and kept private in your deployment
What the record shows
- —Which of your files, steps and parameters produced each finding
- —What was compared, and against which version of the graph
Illustrative workflow, not a product screenshot
AskWhere do our results agree with the published evidence, and where do they not?
BuildMapForge turns your tables into your Company Graph, reviewer-approved
RunDiversity and taxonomic analysis steps on your cohort, once approved
ReasonYour findings compared with MicroMap through shared identifiers
CheckA review pass on what looks new
RecordFindings written back to your Company Graph
Use case 4
A go/no-go your leadership can audit
For r&D leads and portfolio committees.
“Should we move this indication forward, and can we show why later?”
You leave with
- —A one-page evidence summary
- —Designed to keep the decision and its evidence together
What the record shows
- —Designed to show what was known when the decision was made, who decided, and what has changed since
Illustrative workflow, not a product screenshot
AskShould we move this indication forward, and can we show why later?
GroundWhat the graphs hold on the indication, with sources
ReadEvidence on both sides, and its gaps
CheckA review pass on the evidence summary
RecordOperon is designed to record the decision alongside the evidence it rested on
Use case 5
Reproducing an analysis for a partner or regulator
For teams handing results to a partner, a diligence team or a regulator.
“Can someone outside our team check how this result was produced?”
You leave with
- —A record of how the result was produced, run by run
- —An export designed to be checked independently, with an open verifier
What the record shows
- —The pipeline, its version, who ran it and what it produced
- —Which tasks completed, which failed, and the compute they used
Illustrative workflow, not a product screenshot
AskCan someone outside our team check how this result was produced?
RecordEvery run, including runs made outside Operon
CheckThe reviewer's pass, recorded too
ShareDesigned to share the record of the runs behind the result
VerifyDesigned so the other side can check the decision log with an open verifier
Use case 6In development
Running a partner's method without seeing inside it
For method owners licensing a method, and the teams that want to use it.
“Can we use their method on our data without either side exposing what it holds?”
Operon is designed to run partner methods this way. This part is being built now.
You leave with
- —Results from the method, on your data
- —Designed to give both parties a usage record they can see
What the record shows
- —Which method version ran, on what, and when
- —Designed to show this without revealing the method's contents
Illustrative workflow, not a product screenshot
AskCan we use their method on our data without either side exposing what it holds?
RegisterDesigned so the method enters the registry with its owner and licence
RunIt runs inside your Operon deployment
RecordDesigned to record each use for both sides
Bring your question. We'll show you how Operon would work it through.
or emailvkhandavalli@graphomics.com