Corrections, Versioning, and Safety Change Log

Arc-flash software should make errors visible and correctable. This page is the public process for reporting a problem and the record of changes that can affect interpretation, calculation output, or field documents. It covers the calculator, guided-input assistant, label preview, generated PDFs, and standards-linked editorial pages.

Last reviewed: July 19, 2026.

Report a problem

For a calculation issue, include the calculation ID, engine version, input values, selected method, expected result, and the independent calculation or published worked example used for comparison. For a content issue, include the page URL, exact sentence, proposed correction, and a primary or authoritative source. For a document issue, identify the label size or document type and attach a redacted screenshot that shows the defect.

Do not send a facility one-line, employee data, customer data, live sign-in link, payment information, or details that would expose an energized-work plan through a public channel. A calculation ID and redacted values are usually enough to reproduce a software defect. Security vulnerabilities should be reported privately and should not be posted with reproduction details in a public issue.

Until a dedicated support address is provisioned, corrections can be documented through the project owner's normal support channel. The site does not display an unmonitored email address. A report is not considered closed merely because a reply was sent; closure requires a reproducible disposition, evidence, and a change-log entry when the issue can affect other users.

Triage policy

Safety-significant reports have priority. Examples include a wrong equation coefficient, incorrect unit conversion, method applied outside its verified range, clearing-time branch omitted, calculated incident energy mapped to a PPE category, misleading signal-word logic, silent input substitution, or a PDF that drops a governing warning. The first response is containment: disable or clearly warn the affected path, preserve the evidence, and determine which engine versions and stored records may be affected.

The correction then receives a regression test at the lowest useful layer and, where appropriate, an HTTP or document-level test. A qualified reviewer examines changes that alter electrical-safety interpretation. The affected path is not presented as independently reviewed until that review is complete. Editorial corrections receive the same source-trail check, but typographical changes that cannot change meaning do not require an engine release.

Stored records are immutable evidence. The service does not silently replace old results with numbers from a new engine. Each calculation carries its engine version and timestamps. When an earlier output is no longer suitable for field use, the application marks the legacy condition, explains the reason, and directs the user to rerun the assessment. This preserves traceability while preventing an outdated artifact from looking current.

Current change log

July 19, 2026 — method separation and launch hardening

• Removed the conversion of calculated incident energy into NFPA 70E PPE categories. Calculated results now state the incident energy and an equal minimum arc-rating basis. PPE categories appear only on applicable category-method results.
• Removed the automatic DANGER state and hard prohibition previously inferred above 40 cal/cm². New labels use WARNING by default and explain that signal-word selection belongs to the equipment owner's documented hazard-communication policy.
• Removed automatic shortening of clearing times above 2 seconds. The current product scope rejects those inputs and calls for qualified engineering review.
• Added legacy markers for historical records that used superseded category or clearing-time behavior. Existing evidence remains versioned and is not rewritten.
• Reworked the public interface for readable light and dark themes, mobile navigation, visible focus states, responsive tables, clearer input provenance, and a step indicator in the guided assistant.
• Added fail-closed launch checks for mail delivery, pack checkout, Pro checkout, and independent qualified review. Unprovisioned actions are disabled instead of pretending to succeed.
• Added the methodology and corrections surfaces, core tools to the sitemap, private-route crawler controls, stable publisher identity, and updated machine-readable discovery files.

How to verify the current release

Start on the methodology page and compare the stated scope with the input form. Run a known calculation and review both arcing-current branches, the governing case, method, incident energy, boundary, notes, and input provenance. Inspect the label and calculation record rather than relying on the summary card alone. For a calculated case, confirm that no PPE category appears. For a table-method case, confirm the exact equipment row and every condition before accepting the category.

If a change affects a facility decision, use the facility's document-control and management-of-change process. A software change log does not replace review of the actual electrical system. Labels should be reissued only after the underlying assessment has been rerun or otherwise verified by the responsible qualified person.