> For the complete documentation index, see [llms.txt](https://docs.protoboard.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.protoboard.xyz/validate-and-build/how-drc-works.md).

# How DRC works

What the design rule check (DRC) checks, the four harness states, and how results show on the canvas and in Board Review

## Goal

Understand what Protoboard's design rule check (DRC) looks at, what each result means and where you see it.

## When DRC runs

DRC runs continuously. Every change to a part, harness or allocation updates the results within a moment. There's no button to press, and the same board always gives the same result.

## What DRC checks

For each harness:

1. **Is there an interface link?** A harness with no interface pair is not configured.
2. **Are the two interfaces compatible?** Protocol type, roles, domain, electrical ranges (for example voltage ranges that don't overlap) and physical connector, when the part definitions specify them.
3. **Is every required function wired?** Each function the interface requires needs a function link on the harness.
4. **Does every function have a resource?** Each required function needs a pin or port allocated on its part.
5. **Is each interface within capacity?** A part can't carry more instances of an interface than its resources can back.

Optional functions don't need to be wired. With [fan-out](https://docs.protoboard.xyz/editor/harnesses-and-function-links.md#fan-out), every instance on the fanned side needs its own wiring and pins.

## The four states

| State                    | Colour | Meaning                                                                                     | Board Review lane |
| ------------------------ | ------ | ------------------------------------------------------------------------------------------- | ----------------- |
| **Configured**           | Green  | All required functions are linked and allocated                                             | (no issue)        |
| **Partially configured** | Yellow | The interface link exists, but wiring or pins are missing, or an interface is over capacity | **PARTIAL**       |
| **Not configured**       | Grey   | No interface link yet                                                                       | **BLOCKED**       |
| **Incompatible**         | Red    | The interfaces can't connect, or the parts share no compatible pair                         | **BLOCKED**       |

A one-sided link, where only one side has an interface because the other part isn't modelled yet, shows as partially configured. That's acceptable while you design; model the other side to reach Configured.

Over-capacity interfaces are also reported as blocking part issues.

{% hint style="info" %}
In high contrast mode each state also gets its own line pattern, so state never depends on colour alone. The **HARNESS LEGEND** at the right of the canvas explains each state and its fix.
{% endhint %}

## Where you see results

* **On the canvas**: each harness is coloured by its state.
* **In Board Review**: open **Board Review** in the left rail. Issues are listed under **// DRC Issues**, grouped as **BLOCKED** and **PARTIAL**, each with its reasons and a target icon that shows it on the canvas. See [Board Review and review comments](https://docs.protoboard.xyz/validate-and-build/board-review.md).
* **For agents**: ProtoBot and MCP agents run the same check with `run_drc`.

<figure><img src="https://3535233690-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHc6ZGiGpKHrs578383AS%2Fuploads%2Fgit-blob-240c97280491f8fbac018c0fb1d68a240a8a1ffa%2Fdrc-open-board-review.gif?alt=media" alt="The shield icon in the left activity bar is selected and the Board Review panel opens, listing one DRC issue under BLOCKED. On the canvas, the harness between a resistor and an LED is labeled INCOMPATIBLE."><figcaption><p>Board Review with one blocked DRC issue.</p></figcaption></figure>

## Reading the reasons

Each issue lists why the harness isn't configured, for example:

* `No interface link`
* `No compatible interface pairs found`
* `Protocol type mismatch: i2c vs spi`
* `Voltage ranges don't overlap: 4.5-5.5V vs 1.8-3.6V`
* `Side A function 'i2c_sda' not yet assigned to a resource (0/1)`

Some reasons confirm what does match (for example `Matching domain: electrical`); they're context, not problems. For fixes, see [Fixing DRC failures](https://docs.protoboard.xyz/validate-and-build/fixing-drc-failures.md). The full list is in [DRC rules and severity](https://docs.protoboard.xyz/reference/rulesets-and-severity.md).

## What DRC doesn't check

DRC works from the part definitions on your board. It doesn't simulate circuits, check timing or bus loading, or catch a wrong value in a part definition. Check critical numbers against the datasheet, and [report a problem](https://docs.protoboard.xyz/parts/request-or-fix-a-part.md) if a library part is wrong.

## Common failures

<details>

<summary>Every harness is grey</summary>

Drawing a harness doesn't choose what it carries. Select each harness and pick an **Interface pair**.

</details>

<details>

<summary>The issue doesn't clear after I fix it</summary>

Check that you're editing (the status pill says **Editing**) and that the change saved. If the reason mentions a function, look for a second instance or the other side of the harness.

</details>

## Related pages

* [Board Review and review comments](https://docs.protoboard.xyz/validate-and-build/board-review.md)
* [Fixing DRC failures](https://docs.protoboard.xyz/validate-and-build/fixing-drc-failures.md)
* [Harnesses and function links](https://docs.protoboard.xyz/editor/harnesses-and-function-links.md)
* [DRC rules and severity](https://docs.protoboard.xyz/reference/rulesets-and-severity.md)
