Corrections policy
Mistakes happen. What matters is how quickly they are found, fixed and disclosed.
Reporting an error
Every reported error is investigated — whether it comes from a professional or a layperson. The reporting route is the contact page; a reply is usually sent within two working days.
Safety-critical errors
A confirmed error that can lead to an unsafe design — an undersized conductor, too many modules per string, a missing critical warning — is fixed without delay. If an immediate fix is not possible, the affected calculator is taken offline until it is. A wrong safety-critical calculator does not stay online because it brings traffic.
Process
Confirmed errors are pinned down with a regression test so they cannot return. The fix passes the same automated gates as any other change: reference cases, translation completeness, data validation.
Disclosure
Every substantive correction is documented in the public changelog — what was wrong, what applies now, and since when. There are no silent corrections.