Use case
A cited lab knowledge base, not another shared folder
Turn trusted lab documents into a source-grounded knowledge base your team can ask directly.
Who it is for
Research groups that need reusable knowledge across papers, protocols, notes, theses, and reports.
Why this matters
Shared storage preserves files, but not the practical ability to find the right answer and verify the source quickly.
What it helps with
Make frequently reused lab knowledge accessible without losing provenance.
Give the team a common place to ask from approved documents.
Identify gaps where the lab needs better documentation.
How a pilot would use it
- Upload the documents the lab already trusts and references often.
- Ask operational, project-history, or source-checking questions.
- Review citations before using an answer in research work.
Example question
Where did our default preprocessing threshold come from?
The threshold was introduced in the 2021 analysis note after the team compared three settings against the hand-labeled validation subset.
Trust and controls
- Your documents, chunks, and embeddings are treated as sensitive research data.
- Workspace permissions decide who can search and ask.
- It declines when uploaded evidence is not enough.
Current Early Access limits and provider-mode disclosures are documented on the known limitations page.
Start with a focused lab corpus
The strongest pilot starts with documents your lab already trusts: protocols, core papers, theses, project notes, and recurring questions.