Observations, concerns and the Green gate

How a datasheet reading becomes a blocking finding: observations, how they escalate to concerns, and how concerns federate to Trace and gate Green.

View as Markdown (for AI/KB) Whole knowledge base (llms.txt)

Probe distinguishes an observation (a device fact with evidence) from a concern (a board-level worry that can block). This page explains how a low-level reading becomes a finding that the project’s verification gate actually respects.

Observations — device facts with evidence

An observation is a substantiated claim about a part: “this pin is open-drain”, cited from the datasheet. Observations don’t federate automatically — they’re evidence, not decisions. A human confirms or refutes them.

Dispositions — how a finding is decided

Each finding lands in a state: confirmed, refuted, benign, checked or open. A decision invalidates itself when the material it rested on changes — so an old judgement can’t quietly remain after a new take.

Concerns — when a worry should block

An observation escalates to a concern when it rises to a board-level worry. Concerns federate up to Trace and, once confirmed, they gate Green — the project’s verification gate won’t let it through until they’re resolved. A concern can be raised, confirmed, dismissed or withdrawn.

Cite or abstain

The whole model rests on one rule: when something is unknown, Probe doesn’t resolve it with a guess. Either a datasheet or netlist fact is cited, or it abstains and flags the boundary explicitly. A made-up finding and an optimistic dismissal are the same mistake.


Related: read and export findings and the knowledge tree.

Probe is E-Sharp’s design-review engine. Probe serves evidence; the human makes the technical call.

Book a demo of Probe

Show us your board — we review it and go through the findings together.

Prefer to email? info@esharp.se