> For the complete documentation index, see [llms.txt](https://docs.neurolabai.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neurolabai.io/organize-and-compare-research/research-workbenches.md).

# Research Workbenches

{% hint style="info" %}
**Status: In development.** Workbenches describe the direction of reusable research state and are not yet a generally available product promise.
{% endhint %}

A Research Workbench is designed to preserve the context around an investigation, not just its final sentence. It provides a reusable place for the question, selected compounds and targets, filters, model settings, graph state, and references to generated reports.

## What a workbench can organize

The developing workbench model can contain:

* a research goal or working question;
* compounds and molecular targets under review;
* report references and the versions that produced them;
* active evidence and visualization filters;
* knowledge-graph selections and layout state; and
* model or analysis settings needed to interpret the view.

This makes it possible to return to an investigation without treating a screenshot or copied conclusion as the full research record.

## Version-aware by design

A workbench should preserve which model, knowledge-graph release, report schema, and input route produced each result. When a report is regenerated under a newer release, the new artifact should be compared with—not silently substituted for—the earlier one.

## What a workbench is not

A workbench does not prove a hypothesis, merge unlike scores onto one confidence scale, or turn a saved selection into scientific support. It also should not be treated as a substitute for an electronic laboratory notebook or regulated record system unless a future product contract explicitly establishes those capabilities.

Next: [Molecular Portfolios](/organize-and-compare-research/molecular-portfolios.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.neurolabai.io/organize-and-compare-research/research-workbenches.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.