Film creditsA source is not yet a hypothesis.
Varun Sharma on building an analytical resource that helps a scientist or investor decide what evidence to seek next.
Founder perspective | External research and proposed company work are distinguished.
More papers should improve a decision.
I want an analytical resource that earns the reader’s time.
A large collection of papers can look impressive while leaving a developer with the same uncertainty. I want VARUNÉ Bio’s analytical direction to do something more useful: connect a defined question with the evidence that bears on it, the disagreement that remains and the next comparison worth considering.
That begins with a reader. A formulator may need to understand whether two reported results are genuinely comparable. A researcher may need a traceable lead for a study brief. An investor may need to see which uncertainty a proposed milestone would address. The same source record can support those conversations without pretending that they are the same task.
Examine the development decision
A source is not yet a hypothesis.
Open the sequence to examine what a development decision needs.
Identify the exact preparation, its source, and the properties a second laboratory must be able to reproduce.
Explanatory geometry · no simulated or measured performance
Keeping identity, context and permission together.
A useful record carries more than a link.
The FAIR principles connect reuse with findability, access, interoperability and appropriate description, including provenance and licensing (Wilkinson et al., 2016). I see those principles as a starting point for the resource we want to build, not a certification of a completed Bio service.
A public record should make it possible to inspect the original work, identify the version and understand which part was reviewed. It should distinguish an abstract-level reading from a full methods appraisal. That gives the reader a sensible basis for deciding how much weight to place on the summary.
Check whether values belong together.
A dataset becomes more useful when its incompatibilities are visible.
Consider two external experiments that use different material preparations or endpoints. Combining their values into one visual ranking might produce a tidy chart and a weak inference. I would rather the resource explain the mismatch and help a scientist define the comparison that would make the question answerable.
The analytical task should record units, conditions, sample identity and the reported uncertainty before treating observations as comparable. General metrology guidance makes uncertainty part of expressing a measurement result; it cannot repair missing experimental context after the fact (Taylor and Kuyatt, 1994).
From a biological function to a material brief.
The application gives the science its next question.
Write what could be wrong.
A hypothesis earns its place by making a test possible.
I want a source-derived hypothesis to identify the proposed relationship, the conditions in which it is expected and an observation that would challenge it. It should also identify competing explanations. That turns an interesting interpretation into something a suitable research team can examine.
The hypothesis remains ours to investigate; the external paper should not be cited as if it established it. The public resource can make that distinction useful with three separate layers: what the source reports, how we interpret its relevance and what we propose to test next. That is a reading experience with a purpose.
A new item needs a reason to interrupt.
Freshness alone does not make an alert valuable.
An alert could matter because a new method changes the feasible comparison, a correction changes confidence in an earlier result or a new dataset helps define the application. I want those reasons visible. A feed that only repeats titles would give a busy reader more work without helping them decide what has changed.
For any future monitoring service, coverage, refresh dates and review responsibility would need to be clear. A weekly digest, an annual dataset and a continuously updated registry have different rhythms. The site should not imply a real-time service or comprehensive coverage before those operations exist.
Protect the detail that needs protection.
A public analysis should still let the reader understand the question.
I want the public layer to contain sources, bounded interpretation and enough programme context to make a conversation worthwhile. Unpublished methods, partner information or commercially sensitive material can require a different access decision. The route into a confidential discussion should explain the proposed purpose before requesting protected information.
FAIR access principles permit authentication where necessary; they do not require unrestricted disclosure (Wilkinson et al., 2016). For Bio, a future controlled-access layer would need appropriate rights, agreements and a clear account of what the recipient may use. A signed NDA alone would not grant rights in someone else’s research.
A recurring research decision.
The product opportunity should come from repeated value.
One possible starting service is a traceable evidence brief around a formulation or materials decision. Another is a structured source record that a research team can update and reuse. These are propositions to test with prospective users, not launched services or claims that a market has already been secured.
I would judge the first version by whether it helps a user identify a better comparison or a more useful next step. If it does, the discussion can examine delivery, access, pricing and the work needed to maintain it. The ambition is an analytical resource people return to because it improves their decisions.
The difference under investigation.
Turn the scientific question into a comparison with a useful output.
Bring the decision behind the search.
A short, non-confidential introduction can outline the application, the current approach, and where scientific input could help. Scope and next steps would be agreed around the actual project.
Discuss the development questionSources and reading notes.
External work is identified below. Access notes describe the material inspected for this page; company research questions and proposed work are not presented as findings from these sources.
Wilkinson, M.D. et al, 2016Wilkinson, M.D. et al. (2016) The FAIR Guiding Principles for scientific data management and stewardship. Scientific Data, 3, 160018. doi:10.1038/sdata.2016.18.
Findable, Accessible, Interoperable and Reusable principles include persistent identifiers, provenance, licensing and possible authentication.
Scope and limitations: Guiding principles rather than certification or proof of an implemented Bio data service. FAIR does not mean unrestricted commercial reuse.
Open original sourceTaylor and Kuyatt, 1994Taylor, B.N. and Kuyatt, C.E. (1994) Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results. NIST Technical Note 1297.
Measurement results require an account of uncertainty and how it is evaluated and reported.
Scope and limitations: General metrology framework. Individual methods, instruments and uncertainty budgets require suitable scientific review; no Bio calibration or validation is implied.
Open original source