> 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/engineering-and-scientific-assurance/brain-localization.md).

# Brain Localization and Atlas Labels

The brain output head ranks 392 stable parcels: 360 Glasser cortical labels and 32 Tian S2 subcortical labels. The current response adds readable metadata to the top-20 parcel section while preserving the model output contract.

## Response enrichment

Each `brain_top20_parcels_specific` row can now contain:

```json
{
  "parcel": 181,
  "delta": 0.42,
  "network": "Network: Default",
  "anatomy": "cortex",
  "name": "...",
  "section": "...",
  "hemi": "..."
}
```

`parcel` remains the stable identity. Graph region nodes retain stable identifiers such as `parcel_<id>` and may carry the readable label fields as attributes.

## What was validated

* all 392 output positions resolve to the expected atlas label set;
* eight targeted release cases passed;
* the 360-case full deployment suite passed with five skips and no failures;
* response-schema checks passed;
* knowledge-graph, checkpoint, and KEEP-projection contracts passed; and
* checkpoint outputs were equivalent after removing only `name`, `section`, and `hemi`.

This validates the integration and preserves numerical behavior. It is not evidence that brain-localization accuracy improved.

## Interpretation boundary

Atlas labeling improves readability, accessibility, export quality, and cross-view navigation. It does not turn relative model outputs into anatomy measurements, measured activation, functional connectivity, or individual prediction.

***

Next: [Release State and Validation](/engineering-and-scientific-assurance/release-state-and-validation.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/engineering-and-scientific-assurance/brain-localization.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.