∇ProvenDecisions
Ctrl K

Reading an answer

Every number in an answer comes from a solver (a program that finds the best option) or the math kernel, never from a guess. Each answer carries a status label and a verification line.

Status labels

Verification

After solving, ProvenDecisions checks every rule against the answer (feasibility), checks that whole-number variables are whole, and, by default, runs an independent optimality check: the dual problem for a linear program, the optimality (KKT) conditions for a smooth problem. If a check fails, the answer is marked "Not verified" and is not presented as right.

What is proven: the label on every answer

Each answer ends with one short label that says exactly how much is proven:

Duals and sensitivity

A dual value (shadow price) tells you how much the best value changes if one limit grows by one unit, for example one more oven hour. A slack tells you how much of a limit is left unused.

Walkthrough depth 1 to 10

Depth 1 is the answer and a one-line formulation. Depth 3 (the default) is mostly plain-language: decisions, goal, rules. Higher depths add indices and sets, each equation, the code, solver settings, and how to read duals and slacks. Depth 10 is the full derivation. You can change it for any answer.

If an answer looks wrong

Most often a number in the problem was misread or a rule was left out. Look at the formulation ProvenDecisions shows, correct it, and run again. If it still looks wrong, tell us: support re-checks it with the solver and a person on our team reviews anything that is truly wrong.

Try ProvenDecisions free: type, photograph or say an optimization problem; every answer is checked by a solver.

What do you want to optimize?

Type the math, describe it in words, snap a photo or say it. ProvenDecisions builds the model, solves it, checks it and walks you through it.

One constraint per line, or separated by commas. Add integer: x, y or binary: z for whole-number decisions. LaTeX works too.

Try: