> 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-rule-checks-prcs/interrupted-return-path.md).

# Interrupted Return Path

Explanation of the Interrupted Return Path PRC, verifying consistent ground coverage beneath impedance controlled signals to ensure signal integrity and minimize EMI.

### Description

**Interrupted Return Path** determines if the ground plane below a specified net traces overlaps at all relevant points.&#x20;

Relevant points are defined outside a small margin provided in order to account for cutouts around the attached pins and vias.

**Passing Criteria:** \
This check passes if there is complete overlap of both sides of the differential pair with the ground plane on the layer below it at all locations except the last 2\*clearance length endpoints of the trace paths.

**Reporting Units:** \
BOOLEAN

### **Examples**

**Passing Message:**&#x20;

{% hint style="success" %}
Interrupted return path is false
{% endhint %}

**Failing Message:**&#x20;

{% hint style="danger" %}
Interrupted return path is true
{% endhint %}

### Physics Justification

Sufficient ground plane coverage below all traces in a net addresses the following: &#x20;

* **Signal Return Path**  \
  The ground plane provides a low-impedance return path for current, which reduces electromagnetic interference (EMI) and enhances signal integrity. &#x20;
* **Controlled Impedance** \
  The space between the trace and the ground plane determines the trace's **impedance**. This must remain consistent for high-speed signals to prevent reflections and distortion. &#x20;
* **Noise Shielding**  \
  The ground plane acts as a shield, minimizing external noise and preventing crosstalk—the interference between signals.


---

# 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-rule-checks-prcs/interrupted-return-path.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.
