Customer standards and standard packs (admin)

For administrators: how an organisation's own connector standards become checks in Probe via versioned standard packs.

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

This page is for the administrator.

An organisation often has its own connector standards — a fixed pinout, domains and requirements for a particular connector. Probe takes them in as standard packs and turns them into checks.

What a standard pack holds

A pack is versioned and carries the pinmap, domains, requirements and citations for one or more connector standards. A placement becomes a candidate for a standard by being matched on part — never on net name (name matching is a trap). It’s the designer who answers which standard applies, not the AI.

Install and upgrade a pack

Packs are installed over the API, and dry run is the default — you see what would change before anything is stored. So you can preview a new or updated version without risk.

The connector-by-connector check

With the pack in place, the check runs per connector: the actual connectivity is compared against the standard’s pinout, and deviations are raised, pinned at the connector.

Confidentiality: an installed pack may be transcribed from a named partner’s document. Don’t reuse or mention a customer’s standard in material other customers see — describe the mechanism generically.


Related: connector families and interconnect and the seam.

Probe is E-Sharp’s design-review engine. The designer answers which standard applies — Probe checks against it.

Book a demo of Probe

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

Prefer to email? info@esharp.se