Scope and responsibility
The coolmath Editorial Team owns topic selection, first-party testing, factual review, disclosure, updates, and corrections for game descriptions and guides. An organizational byline is used because named contributors and credentials have not been confirmed. We do not create fictional biographies, classroom experience, qualifications, or endorsements.
Game testing method
A release check covers the main rule, correct and incorrect outcomes, input methods, restart or recovery, responsive behavior, keyboard focus, console errors, page errors, failed requests, and horizontal overflow. The current automated browser pass tests all fifteen games at 1280 by 800 and 390 by 844 pixels. Human editorial review then asks what mathematical action is repeated, what prior knowledge is required, and what the game cannot establish.
Sources and claims
Direct observations are described as tests of the current coolmath build. Mathematical examples show their calculations so a reader can reproduce them. Changeable external facts should use primary or authoritative sources and a verification date. We remove or qualify claims that cannot be verified and distinguish a recommendation from a guaranteed outcome. Scores, completion time, and successful play are not represented as proof of mastery.
Article acceptance
A guide is publishable only when it addresses a real user task and demonstrates target-market localization, verifiable evidence, a concrete case, reasoned editorial judgment with limits, and accountable authorship. It must also provide aligned metadata, a canonical URL, relevant imagery with known provenance, internal links, publish or review dates, and a correction route. Thin, spun, copied, or mechanically varied pages do not pass.
Automation and AI assistance
Automation can identify broken links, missing metadata, layout overflow, browser errors, inconsistent facts, or repetitive language. Generative assistance may support a draft or an original visual, but the responsible team must check the finished claim, example, route, image context, and live behavior. Assistance is never presented as first-hand human experience, professional qualification, or an independent source.
Conflicts and monetization
Advertising, sponsorship, affiliate payment, or free access must not change a test result or educational judgment. A future paid relationship must be disclosed where a reader would reasonably expect it. Sponsored material must be clearly labeled and separated from Play, Restart, Full Screen, navigation, and answer controls. The current build contains no advertising or affiliate code.
Corrections and updates
Send correction reports to [email protected] and identify the exact URL, disputed statement or behavior, expected result, and supporting evidence. We review the current page and reproducible evidence, correct material errors, and change the substantive update date only when the content changes. Compatibility, privacy, safety, rights, or materially different educational-fit corrections receive priority. Typographic changes do not justify presenting an old page as newly reviewed.