Editorial Policy
The calculator and its articles are written to match what the code can actually do. I avoid describing unsupported equation classes as if they worked.
Calculator methodology
Equation results come from deterministic solver code. Numeric roots are checked against the original equation when the supported parser permits it. Rational equations preserve denominator restrictions, and radical candidates are filtered for extraneous roots.
Graphs, LaTeX, and OCR
A graph is a visual check, not a proof. LaTeX support is a documented subset rather than a complete TeX engine. OCR is treated as untrusted transcription until the user reviews the recognized equation.
Localized content
Localized pages are written around the terms people actually use for equation solving in that language. A language route should not be published merely because navigation labels were translated; the visible calculator instructions, page copy, metadata, and guides need to read naturally together.
Corrections and tests
Confirmed mathematical bugs should be accompanied by a code or content correction and, where practical, a regression test using the reported input. Material content changes can update the page review date.
Editorial review checklist
- Each worked example is checked against the solver's stated algebraic method and its substitution verification.
- Pages state supported forms and limitations instead of implying that every equation can be solved.
- Educational claims and feature explanations are linked to public references when an external source is useful.
- Confirmed errors are corrected, and reproducible cases are added to regression tests when practical.