> For the complete documentation index, see [llms.txt](https://docs.quilter.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quilter.ai/physics-constraints/ground-nets.md).

# Ground Nets

Ground nets provide return paths and reference planes for signals. Use this section to choose your primary ground and to request isolated ground pours

***

### Automatic Detection

Quilter lists nets it identifies as grounds using built in detection rules using naming convention (GND, DGND, ...) and net classes.

### Constraint Details

* **Primary Ground:** the net used for ground layers in your stackup. Only one net can be the Primary Ground
* **Use Region Pour:** pours this ground in the shape of the placement region that contains its components. Use it for galvanically isolated sections.

A net can't be both the Primary Ground and a Region Pour

### Requirements for region pours

* Your stackup must have at least one ground layer.
* The placement region must be placed inside the board outline.
* Every component on that ground net must be in a placement region.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.quilter.ai/physics-constraints/ground-nets.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
