📐

Ask a student to differentiate $x^2 + 3x$ and they'll write $2x + 3$. Ask most AI math tools the same question and you'll usually get the same answer — but occasionally you'll get something subtly wrong, with no indication that anything went wrong at all. That difference matters more than it might seem.

The problem with approximate tools

Most digital calculators and many AI-based tools work by producing a likely answer — one that matches the pattern of what a correct answer looks like. When this works, it's seamless. When it doesn't, the result looks exactly the same as a correct one. A student who doesn't already know the right answer has no way to tell the difference.

This creates a specific kind of harm for learning: a confidently stated wrong answer is worse than no answer at all. It doesn't just leave a gap in understanding — it actively fills the gap with something incorrect. A student who copies a wrong answer, submits it, and gets it marked wrong learns nothing except that the tool can't be trusted.

Zeretis is different because it doesn't produce likely answers. It computes exact ones — or tells you it can't find one. There's no in-between.

What "exact" actually means

When Zeretis solves $\int x^2 \, dx$, the result is $ rac{x^3}{3} + C$. Not $0.333x^3$ — the exact fraction, preserved symbolically. When it solves $\sqrt{8}$, the result is $2\sqrt{2}$, not $2.828...$. These aren't aesthetic preferences — they matter for downstream calculations. If you're working through a multi-step problem and one intermediate step rounds, that rounding error compounds through every step that follows.

For a student checking their homework, this means the answer Zeretis gives is the same form their teacher expects to see. Fractions stay as fractions. Surds stay as surds. The result looks like math, not a calculator output.

Real examples from students

Here's what using Zeretis actually looks like in practice:

Example — GCSE algebra
Student types solve x squared minus 5x plus 6 equals 0 → x = 2, x = 3
Step 1 — factor (x − 2)(x − 3) = 0
Step 2 — zero product property x − 2 = 0 or x − 3 = 0

The student typed their problem in plain English — no special syntax. They got the answer and every step. They can compare their own working against the solver's output step by step. If they made a mistake, they can see exactly where.

Example — A-level calculus
Student types integrate x^2 * e^x dx → x²eˣ − 2xeˣ + 2eˣ + C
Method — integration by parts, applied twice Full working shown step by step

Why the steps matter as much as the answer

The answer on its own is close to useless for learning. A student who sees "$x = 2, x = 3$" without understanding why can copy it and hand it in — but they'll fail the next question with a slightly different structure. The steps are what turns a solver into a learning tool.

Every Zeretis result includes the full working — each transformation labelled with the rule that was applied. A student learning integration by parts sees the method, not just the outcome. They can follow each step, pause, ask themselves "do I understand why that happened?", and re-read if not. It's the same as a textbook worked example, except it works for any problem they enter.

The goal isn't to give students answers. It's to give them enough worked examples, on demand, that the method becomes familiar. Use the solver to understand — then close it and try the next problem yourself. That's how you actually prepare for an exam.

A tool students and parents can trust

Because Zeretis only responds to mathematical input — it can't discuss other topics, generate essays, or be used for anything other than solving math — it's safe for independent student use at any age. No harmful content is possible because the scope of the tool makes it impossible, not because of a filter. Parents can hand it to a child with confidence. Teachers can assign it for home use without worrying about what else it might produce.

And because results are consistent — the same problem always gives the same answer — a teacher who wants to check what a student saw can run the same problem and verify the exact output. There's nothing unpredictable to explain.