> 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/future-directions.md). # Where Neurolab Is Going Neurolab is rapidly growing from a single-report investigation workflow into a broader environment for evidence-aware research programs. The direction is organized around a few durable themes rather than a fixed list of release promises. ## From Inference Reports to Persistent Research Programs User accounts, personalization settings, and the upcoming Research Workbench feature are intended to let researchers preserve goals, compounds, targets, filters, model settings, graph state, and report references. The objective is continuity: a useful investigation program should be persistent, resumable, and comparable without losing the conditions that produced it. ## From Single Compound to Structured Comparisons Molecular Portfolios are being designed to group saved cohort forecasts and compare selected fields at fixed model and knowledge-graph versions. The first goal is careful human comparison, not automated winner selection or opaque batch scoring. For example, a researcher may be investigating an existing drug discovery initiative that has a pipeline with several compounds targeting the same receptor. The objective of Molecular Portfolios is to let this researcher compare the forecasted brain effects of *each* compound across the entire initiative, over multiple biological scales, to surface promising repurposing candidates and to help differentiate among (positive and negative) forecasted secondary effects of compounds that show similar on-site activity. ## From Inference Navigation to Comprehensive Data Analysis Section Inspector and Data Explorer already provide bounded natural-language operations over a report. Data Studio extends that direction toward more flexible comparison, visualization, and evidence-aware analysis while preserving the underlying values and provenance. ## From maps to guided brain-system exploration Brain Explorer is evolving toward clearer regional navigation, guided tours, reference-report context, and explicit views of networks, tracts, circuits, and supporting evidence. Predicted, measured, literature, density, circuit, and reference channels remain distinct. ## From application use to integration The separate API publication describes a public contract preview for future integrations. A public gateway, authentication policy, quotas, and service commitments will be documented when they are ready for external use. Next: [Run Your First Query](/start-using-neurolab/first-query.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/future-directions.md?ask=&goal= ``` `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.