> 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/overview.md).

# Overview

Overview of Physics Rule Checks (PRCs) applied by Quilter to validate user-defined physics constraints.

Physics rule checks (PRCs) validate candidates by ensuring that the critical parameters for each physics constraint are satisfied. Quilter produces PRC reports for every layout candidate it examines.

During Circuit Comprehension, Quilter reads your schematic and input board file to automatically detect  [Physics Constraints](/physics-constraints/overview.md) that capture the core physics concerns in your design. Quilter generates a set of PRCs for each identified constraint as a way to evaluate the implementation of that constraint in the layout candidates that it generates.

For example, [Differential Pairs](/physics-constraints/differential-pairs.md)are checked to validate appropriate length matching, tightly coupled spacing, and ground plane overlap.

Continue reading for a complete overview of supported Physics Rule Checks and the associated physics constraints that they support.

### PRCs by Constraint Type

<table><thead><tr><th width="312.484375">Physics Constraint</th><th>Applied PRCs</th></tr></thead><tbody><tr><td><a data-mention href="/physics-constraints/power-nets.md">Power Nets</a></td><td><ul><li><a data-mention href="/physics-rule-checks-prcs/overheated-length.md">Overheated Length</a></li></ul></td></tr><tr><td><a data-mention href="/physics-constraints/timing-sensitive-signals.md">Timing-sensitive Signals</a></td><td>Coming soon</td></tr><tr><td><a data-mention href="/physics-constraints/single-ended-impedance-control.md">Single-ended Impedance Control</a></td><td><ul><li><a data-mention href="/physics-rule-checks-prcs/invalid-width-span.md">Invalid Width Span</a></li><li><a data-mention href="/physics-rule-checks-prcs/ground-plane-overlap.md">Ground Plane Overlap</a></li></ul></td></tr><tr><td><a data-mention href="/physics-constraints/differential-pairs.md">Differential Pairs</a></td><td><ul><li><a data-mention href="/physics-rule-checks-prcs/ground-plane-overlap.md">Ground Plane Overlap</a></li><li><a data-mention href="/physics-rule-checks-prcs/uncoupled-spacing.md">Uncoupled Spacing</a></li><li><a data-mention href="/physics-rule-checks-prcs/length-mismatch.md">Length Mismatch</a></li></ul></td></tr><tr><td><a data-mention href="/physics-constraints/bypass-capacitors.md">Bypass Capacitors</a></td><td><ul><li><a data-mention href="/physics-rule-checks-prcs/pin-distance.md">Pin Distance</a></li><li><a data-mention href="/physics-rule-checks-prcs/trace-path-length.md">Trace Path Length</a></li><li><a data-mention href="/physics-rule-checks-prcs/layer-switch-count.md">Layer Switch Count</a></li><li><a data-mention href="/physics-rule-checks-prcs/ground-plane-overlap.md">Ground Plane Overlap</a></li></ul></td></tr><tr><td><a data-mention href="/physics-constraints/crystal-oscillators.md">Crystal Oscillators</a></td><td><ul><li><a data-mention href="/physics-rule-checks-prcs/pin-distance.md">Pin Distance</a></li><li><a data-mention href="/physics-rule-checks-prcs/trace-path-length.md">Trace Path Length</a></li><li><a data-mention href="/physics-rule-checks-prcs/layer-switch-count.md">Layer Switch Count</a></li><li><a data-mention href="/physics-rule-checks-prcs/ground-plane-overlap.md">Ground Plane Overlap</a></li></ul></td></tr><tr><td><a data-mention href="/physics-constraints/switching-converters.md">Switching Converters</a></td><td><ul><li><a data-mention href="/physics-rule-checks-prcs/pin-distance.md">Pin Distance</a></li><li><a data-mention href="/physics-rule-checks-prcs/trace-path-length.md">Trace Path Length</a></li><li><a data-mention href="/physics-rule-checks-prcs/layer-switch-count.md">Layer Switch Count</a></li><li><a data-mention href="/physics-rule-checks-prcs/ground-plane-overlap.md">Ground Plane Overlap</a></li></ul></td></tr></tbody></table>

### PRC Results

<figure><img src="https://1761213452-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL9R6Vsa5jGn27oTws0tG%2Fuploads%2FLNiqBrdrIqkSdpZSEZnZ%2Fimage.png?alt=media&amp;token=906da8e5-4888-41dc-aa58-1368e2dcb9a7" alt=""><figcaption><p>Example PRC result for a Bypass Capacitor constraint</p></figcaption></figure>

During the review step, you will see passing and failing PRCs alongside candidates, allowing you to be confident that the design will work as expected. For failing PRCs, the documentation for each PRC provides more insight into the listed error.

For more information on interpreting PRC results, see [Reviewing PRCs](/reviewing-prcs.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 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/overview.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.
