> 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/examples-and-use-cases/multiscale-evidence-investigation.md).

# Trace a Multiscale Hypothesis

Neurolab can organize an evidence-linked hypothesis from molecular targets to brain systems. It does not prove a causal chain and does not run a validated whole-brain simulation.

## Example workflow

1. **Start with the route.** Confirm whether the compound ran through the known GNN or the structure/receptor-conditioned route.
2. **Inspect the receptor profile.** Separate model-derived, retrieved, and caller-provided receptor relationships. Conservative sign handling excludes negative or noncausal relations from positive receptor evidence.
3. **Review MoA and cognition rankings.** Use Section Inspector to preserve raw ranks, scope, and reliability.
4. **Open the evidence graph.** Follow report pointers through support links to evidence records and sources. A graph path is typed context, not the model’s hidden reasoning trace.
5. **Compare CircuitFramework context.** Treat receptor-to-region, tract, and cognitive relationships as composed hypotheses under their stated evidence.
6. **Open Brain Explorer.** Compare channels without fusing raw GNN ranks, receptor density, circuit localization, literature, or measurement into one map.
7. **Record uncertainty.** Keep abstention, missing support, inactive reference paths, and release identities with the conclusion.

***

Next: [System Architecture](/engineering-and-scientific-assurance/system-architecture.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/examples-and-use-cases/multiscale-evidence-investigation.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.