# The rulebook and the guides

> What Probe checks: deterministic rules for unambiguous facts and guided checks for reasoning — and how your organisation adds its own.

_Source: E-Sharp (esharp.se) · Probe guide_


Probe's strength isn't a large library of special-case rules, but a complete frame to reason over. But two kinds of check exist, and they do different jobs.

## Deterministic rules vs guided checks

- **Deterministic rules** cover unambiguous, mechanical facts: shorts, a breach of a truth table, missing pull-ups, drive conflicts. The engine owns them and they give a definite answer.
- **Guided checks (guides)** are the encoded reviewer skill — where judgement is required. A guide is triggered by a condition and carries a **check battery** (scope, ask, gather, resolve, severity) that your AI works through.

The rulebook currently holds around eighty deterministic rules and around sixty guides (you see the exact counts in the rule view). One of the rules is deliberately out of scope: pure geometric DFM, which is left to the CAM tools.

## Read a guide

A guide shows its walkthrough and its checks. That's how you see *what* Probe actually checks for a given type of block.

## Add your own checks

Anyone can write a **rule draft** that activates nothing live; an administrator **promotes** it to a living guide. A single check can be added or replaced with version protection, so two people don't overwrite each other.

> To confirm: whether rule drafts/promotion should be a customer feature or internal to E-Sharp only is an open question (see the plan).

---

Related: [the knowledge base](/en/probe/support/the-knowledge-base) and [measure the review against your change log](/en/probe/support/measure-against-your-change-log).

*Probe is E-Sharp's design-review engine. The engine owns the mechanical rules; the reasoning is done per frame by the AI.*
