> 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/beta-scope-and-responsible-use.md).

# Intended Use and User Responsibilities

Neurolab is a research and hypothesis-generation system. The system's inference outputs are designed and specifically formatted to help researchers organize questions, increase the efficiency of new and existing drug development pipelines, and discover promising area of scientific inquiry with potential commercial applications. 

{% hint style="warning" %}
Information provided by Neurolab is for research purposes only. The Neurolab system's inference outputs do not constitute medical or clinical guidance.
{% endhint %}

## Intended Use

Intended uses of the Neurolab application include:

* exploring model-ranked mechanism, cognition, usage, safety, and brain-related outputs;
* tracing report support into source and graph context;
* comparing a prediction with retrieved records without conflating the two;
* generating hypotheses for expert review;
* identifying uncertainty, missing evidence, and validation gaps;
* developing research interfaces or benchmarks from exported artifacts; and
* planning literature review or experiments with a qualified human in control.

Neurolab helps organize a research process. The researcher remains responsible for checking scope, limitations, and primary sources before using an output in downstream work.

## Product Boundaries

Neurolab is *not* intended to:

* diagnose, treat, or make decisions for an individual patient;
* recommend a medication, supplement, route, schedule, or dose;
* determine whether a compound is safe or effective;
* replace clinical, toxicological, regulatory, or primary-source review;
* present model rankings as established biological or clinical facts;
* infer measured brain activation from a displayed hypothesis map; or
* automate consequential actions without independent review.

## User Guidance

To get the most out of Neurolab, users are encouraged to:

1. Record whether the result came from the known, structure, or receptor-conditioned route.
2. Read reliability, applicability, abstention, and caveats before ranked values.
3. Preserve model, graph, schema, and generation identifiers with exported results.
4. Keep caller-supplied receptor assumptions attached to downstream interpretations.
5. Follow support links to the exact report field they address.
6. Review primary sources before repeating a scientific claim.
7. Report outputs that appear overconfident, unsupported, incorrectly sourced, or unsafe.

## Data and Access Boundary

Queries and report-grounded questions + LLM interactions within the application are processed by application services. Do not submit personal health information, confidential patient data, unreleased proprietary structures, or other sensitive material unless the applicable access and data-handling terms explicitly permit it.

Account and storage capabilities can change during the beta. Preserve a local export of any research artifact that must be retained, and review the current privacy and access terms before relying on saved state.

## Neurolab's Conversational Research Assistant

Neurolab is designed around the principle that researchers should receive deterministic output *before* LLM interaction. Therefore, the application's conversational layer becomes operable after the system's structured inference output completes. \
\
The conversational assistant utilizes customizable context to further explain and discuss specific report fields and help formulate follow-up questions. During LLM interactions, the assistant does not run a second hidden scientific model, upgrade a hypothesis into a fact, or independently verify a pasted structure. The answers provided by the LLM is only as grounded as the context and source material supplied to it.

Next: [Where Neurolab Is Going](/future-directions.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/beta-scope-and-responsible-use.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.