How these products are built, and what the evidence does and does not mean.

The inclusion rule

This is the whole product in one paragraph.

A value is published only if it is either VERIFIED_DIRECT — the value is stated on the cited source and the exact wording is reproduced on the evidence row — or DERIVED_DETERMINISTIC — the value follows mechanically from stated facts by a single recorded rule, with the rule shown. Everything else is withheld: values that are only analytically inferred, values on which two sources genuinely disagree, and values whose status the sources leave unclear. Those rows are counted and disclosed rather than quietly dropped or quietly kept.

Why the withheld rows are the point

A scraped database and a research product look identical until you ask what happened to the uncertain values. Here they are counted, and the count is published next to the headline. A buyer can therefore see both the size of the evidenced set and the size of the set that was set aside.

What a blank means

An empty cell or the word UNKNOWN means the sources reviewed did not establish the fact. It does not mean the capability is absent, and it is not a negative finding. Missing data is left missing rather than filled by assumption.

Dates

Every evidence row carries the date the source was checked. Each product states the range of those dates. These are dated snapshots, not feeds.

What these products are not

• Not a price list, lead-time guide, availability feed or supply assurance.
• Not a supplier qualification, approval or ranking.
• Not engineering, procurement, legal, safety or compliance advice.
• Not an introduction or outreach service.
• Not comprehensive global coverage, and not current beyond the stated coverage date.

Publication hygiene

Packaging is applied to a frozen build and never edits it. Before release, each package is scanned for internal build commentary, internal file paths and build-only columns; any record that exists only for the build's own bookkeeping is withheld, and withheld records are named in that package's QC report. The canonical source hashes are verified unchanged in the same report.

Verification

Each package is checked mechanically for: canonical source integrity, unambiguous classification of every published row, a source URL on every published row, workbook and PDF integrity, absence of formulas and internal fields, and the absence of placeholder or internal text. The QC report ships inside the package folder, not just here.