> 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/molecular-portfolios.md).

# Molecular Portfolios

{% hint style="info" %}
**Status: In development.** Molecular Portfolios are being developed as a comparison and organization workflow; availability may vary during the beta.
{% endhint %}

Molecular Portfolios are designed to group saved forecasts so researchers can compare a focused set of compounds under explicit model and knowledge-graph versions.

## Intended comparison workflow

The developing experience is centered on small, reviewable sets of molecules—typically two to twelve at a time. A portfolio can help compare fields such as:

* mechanism-of-action rankings;
* reliability and evidence coverage;
* brain lobe or network summaries when available; and
* the route and release identity associated with each forecast.

Saved forecasts can be organized, archived, restored, and revisited without erasing their original version context.

## Compare like with like

Before comparing two results, confirm that they use compatible routes, model releases, graph releases, schemas, and output heads. A higher raw score for one compound does not imply a larger biological effect, better therapeutic potential, or stronger clinical evidence.

## Human review remains central

The first purpose of a portfolio is transparent comparison. It is not an automated molecule-ranking engine, a batch-screening claim, or an experiment-selection verdict. Researchers remain responsible for reviewing evidence scope, uncertainty, and primary sources for every forecast.

Next: [Data Studio](/organize-and-compare-research/data-studio.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/molecular-portfolios.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.