# The knowledge base: facts, claims and gaps

> How knowledge is built up in Probe, how sources are weighed against each other, the difference between factual and normative claims, and how gaps are caught.

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


Probe collects what's known about parts and design in a knowledge base where every fact carries its source and its weight. That's how "we read something" becomes "we understand this, and can cite why".

## Facts with source and weight

Each fact is weighted on a ladder by source, e.g.: human highest, then measured/netlist, then datasheet/schematic, and lowest AI extraction and AI inference. A fact can be disputed and withdrawn — nothing is sacred just because it was once written.

## Design level or board level

Knowledge can apply to a whole design line or a single board. What applies to the design is reused wherever it appears; what applies to a board stays there.

## Factual and normative claims

- A **factual** claim describes how something *is*.
- A **normative** claim says how something *should* be. A normative claim requires a review date (at most twelve months out) and confirmation by a second person before it may raise a *fault* — so an opinion doesn't quietly become a block.

## Gaps — when no source answers

When no source can answer, a **gap** is recorded instead of a guess. A gap is an honest hole that can be worked away later, not a void filled with assumptions.

## Reuse across boards

Knowledge gathered on one board benefits the next (the reuse effect). The more the fleet is reviewed, the more is already cited the next time.

---

Related: [the datasheet corpus lifecycle](/en/probe/support/datasheet-corpus-lifecycle) and [the rulebook and the guides](/en/probe/support/the-rulebook-and-the-guides).

*Probe is E-Sharp's design-review engine. A gap is recorded honestly — it isn't filled with a guess.*
