> 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/reference/rulesets-and-severity.md).

# DRC rules and severity

Reference for every DRC harness state, the reasons DRC reports, part-level issues and how they map to Board Review lanes

## Goal

Look up exactly what each DRC state and reason means. For a walkthrough, see [How DRC works](https://docs.protoboard.xyz/validate-and-build/how-drc-works.md); for fixes, [Fixing DRC failures](https://docs.protoboard.xyz/validate-and-build/fixing-drc-failures.md).

## Harness states

Each harness has exactly one state.

| State                    | Canvas | High contrast pattern | Board Review |
| ------------------------ | ------ | --------------------- | ------------ |
| **Configured**           | Green  | Solid                 | Not listed   |
| **Partially configured** | Yellow | Long dashes           | **PARTIAL**  |
| **Not configured**       | Grey   | Dots                  | **BLOCKED**  |
| **Incompatible**         | Red    | Short dashes          | **BLOCKED**  |

## How a state is decided

DRC checks each harness in this order and stops at the first state that applies:

| Check                                  | Result if it fails                                                      | Reasons you'll see                                                                                               |
| -------------------------------------- | ----------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| The harness has an interface link      | Not configured, or Incompatible when the parts share no compatible pair | `No interface link`, `Missing endpoint parts`, `Missing part definitions`, `No compatible interface pairs found` |
| Both sides have an interface           | Partially configured                                                    | `One-sided link: only side A has an interface…`                                                                  |
| Both interface definitions exist       | Partially configured                                                    | `Missing interface definitions`                                                                                  |
| The interfaces are compatible          | Incompatible                                                            | See the compatibility table below                                                                                |
| Each interface is within capacity      | Partially configured                                                    | `Interface '…' is over capacity (used/capacity)…`                                                                |
| Every required function has a resource | Partially configured                                                    | `Side A function '…' not yet assigned to a resource (have/needed)…`                                              |
| Every required function is wired       | Partially configured                                                    | Function wiring reasons, including per-instance reasons for fan-out                                              |

If every check passes, the harness is **Configured**. Functions marked optional in the part definition don't need wiring or resources.

## Compatibility checks

| Check              | Fails with                                                                                   |
| ------------------ | -------------------------------------------------------------------------------------------- |
| Protocol type      | `Protocol type mismatch: A vs B`, `Missing protocol information`                             |
| Roles              | `Incompatible protocol roles: … cannot connect to …`, with the valid pairs for that protocol |
| Net-like protocols | Connect only to electrical interfaces                                                        |
| Domain             | `Domain mismatch: A vs B`                                                                    |
| Electrical ranges  | `Voltage ranges don't overlap: …`                                                            |
| Physical connector | `Incompatible connector types`, `Incompatible connector genders`, `Pin count mismatch`       |

Electrical and physical checks run only when both part definitions specify those values. Reasons such as `Matching domain: electrical` or `Compatible connector type` record checks that passed.

## Part-level issues

Besides harness states, DRC reports issues on parts:

| Code                      | Severity | Meaning                                                               |
| ------------------------- | -------- | --------------------------------------------------------------------- |
| `INTERFACE_OVER_CAPACITY` | Blocking | A part has more instances of an interface than its resources can back |

## Kits

On a board restricted to a kit, Board Identity shows when you've placed more of a part than the kit contains. This is advisory and doesn't change harness states. See [Board Identity, requirements and kits](https://docs.protoboard.xyz/editor/board-identity.md).

## Related pages

* [How DRC works](https://docs.protoboard.xyz/validate-and-build/how-drc-works.md)
* [Fixing DRC failures](https://docs.protoboard.xyz/validate-and-build/fixing-drc-failures.md)
* [Interfaces and Harnesses](https://docs.protoboard.xyz/reference/interfaces-and-harnesses.md)
