Current status: The correction workflow is defined for the public static site. The contact channel remains pending until mailbox delivery, privacy, retention, and abuse controls are verified.
Prepare a useful report
Record enough detail for another person to reproduce the issue.
| Field | What to include |
|---|---|
| Page | Full URL and page title |
| Issue location | Calculator field, result, formula line, table row, heading, statement, source, or link |
| Calculator state | Unit system, every input, optional assumptions, result shown, and result expected |
| Evidence | Independent calculation, official source, project specification, manufacturer data, or supplier document |
| Context | Country, date, product, material condition, browser, and device when relevant |
| Impact | How the issue could affect quantity, interpretation, ordering, safety boundary, or trust |
Keep sensitive project, customer, payment, identity, and location details out of the report unless the future contact process specifically requests and protects them.
Issue classes
| Class | Examples | Initial action |
|---|---|---|
| Calculation | Formula, conversion, rounding, validation, unit switch, or stale result | Reproduce with recorded inputs and independent fixtures |
| Technical claim | Material state, specification interpretation, source scope, or limitation | Review the governing source and assigned technical scope |
| Editorial | Ambiguous wording, unsupported statement, example, attribution, or outdated fact | Trace the claim map and page revision |
| Link or interface | Broken route, inaccessible control, layout overflow, schema mismatch, or browser error | Run the build, crawl, and rendered-page checks |
| Privacy or legal | Data handling, disclosure, rights request, or policy conflict | Restrict exposure and route to the responsible policy owner |
Verification workflow
- Log the report with the affected page and current revision.
- Reproduce the calculation or locate the exact claim, interface state, or policy text.
- Compare the result with the formula specification, fixtures, source scope, and rendered output.
- Classify the finding as confirmed, unconfirmed, expected behavior, source disagreement, or out-of-scope project decision.
- Assign the correction and applicable editorial, calculation, technical, privacy, or legal review.
- Rerun affected tests, rebuild the site, regenerate the sitemap, and validate internal links.
- Record the outcome and update the affected page when the change is material.
Calculator corrections
A confirmed formula, conversion, unit, validation, or rounding error triggers a source-code correction and regression fixture. Related examples and pages are checked for the same logic. The corrected tool passes its normal, boundary, invalid, unit-switch, and rendered tests before release.
Editorial and source corrections
A confirmed factual, attribution, source-scope, or interpretation error triggers an update to the source record and affected copy. A source disagreement is documented with the governing market, date, product, specification, or authority needed to resolve it.
Visible correction notices
| Change level | Visible handling |
|---|---|
| Minor copy edit | Correct the wording and update the page date when the meaning or user action changes |
| Material factual change | Explain what changed, why, and which source or review supports the revision |
| Calculation change | Explain the affected formula or behavior, update fixtures, and identify the corrected version date |
| Temporary uncertainty | Keep the page outside the index, label the unresolved scope, or remove the affected result from use |
Response and status
Reports receive priority according to potential user impact and reproducibility. The future contact workflow will acknowledge receipt and provide the recorded outcome when a reply address is available. Response timing remains uncommitted until the monitored channel is active.