Validation methodology

A tool is only as trustworthy as the process behind it. This is that process, stated so you can decide how much weight to give any result.

1. STEP 01

   Method definition

   Before code is written, the calculation method is written down in plain language with the equations used, the assumptions baked in, and the standard or textbook the method follows. That statement appears on the lab page as the methodology note.

2. STEP 02

   Worked-example comparison

   Results are compared against published worked examples, textbook problems, or hand calculations. Disagreements are resolved before publication or the tool ships with an explicit caution.

3. STEP 03

   Fixture regression

   Each tool has stored input/output fixtures. Any presentation or interface change is re-run against those fixtures and must produce identical numeric output. Presentation work never silently changes engineering math.

4. STEP 04

   Standards citation review

   Every reference is checked for the correct standard, edition, and article or section. Citations name the edition because requirements change between editions.

5. STEP 05

   Accessibility and interface check

   Keyboard operation, focus order, landmarks and labels, contrast, touch target size, and behaviour down to a 320 px viewport are checked before a tool is marked Available.

6. STEP 06

   Subject-matter review

   Where a subject-matter expert has reviewed the method and results, the tool shows SME reviewed. Where that review is scheduled but incomplete, it says so. We never imply a review that has not happened.

What each validation label means

Independently reviewed

A reviewer outside the build team has reviewed and signed off on this release.

SME reviewed

A subject-matter expert on the build team has reviewed this release against its referenced sources.

SME review in progress

A subject-matter expert review of this release has started but is not complete.

Automated checks only

Automated load, runtime, and accessibility checks passed on the recorded date. No subject-matter expert has reviewed the engineering content.

What we do not claim

• We do not certify, approve, or stamp anything. No output is an engineering deliverable.
• We are not affiliated with NFPA, NETA, IEEE, or IEC, and we do not speak for them. Alignment language means our tools follow the referenced method, not that a body has reviewed us.
• We do not reproduce code tables verbatim. Values are computed and presented as results with a citation so you can verify them in the source document you own.
• We do not guarantee an edition is current for your jurisdiction. Adopted editions vary locally; check what your authority having jurisdiction enforces.

Believe a result is wrong? Report a technical issue — corrections are published in the changelog.