Sources

Where the data lives

Every fact on the site comes from a YAML file: one row per provider, exam, vendor course, cooling topic, learning-path step, vocabulary term, event or leasing requirement. There is no database and no CMS — the YAML files in the site's own git repository are the whole store. Each collection is checked at build time against a schema; a row with a figure carrying no source or no checked date fails the build.

Verified and unverified

Every row carries a confidence value. Verified means the fact was checked directly against the entity's own source — its own website, filing or documentation — and matched. Unverified means the fact could not be confirmed against a primary source, or came from a secondary source only; an unverified row also carries a note saying what could not be confirmed, and the site renders an "unverified" badge rather than hiding the gap. Nothing is guessed: if a number, price or URL can't be confirmed, the row is marked unverified with a note instead of being filled in with a best guess.

What a checked date means

The checked date is the last time a human or an agent actually opened that row's source URL and confirmed the fact against it. It is not the date the row was added, and it is not a promise the fact is still true today — it is a record of when it was last looked at.

Staleness

Over 180 days, the site marks a row's "last checked" date in amber — a nudge, not a problem. Over 365 days, the build emits a warning. In both cases staleness never fails the build: the site must not break by standing still, so a page that hasn't been re-checked in a while stays up, visibly flagged, rather than disappearing or blocking a deploy.

Company figures are claims, not audits

Prices, capacities, specs and dates published by a company about itself are that company's own claim, not an independently audited fact. The site links to the primary source so readers can judge for themselves; it does not represent vendor-published figures as verified by anyone other than the vendor.

Licence

Content and data CC BY 4.0. Build code MIT.

Sending a correction

Use the corrections page, linked from every section of the site. A source URL is required — a correction with no source to check it against can't be accepted. Accepted corrections are committed with a source and a checked date within a week.