All demonstrationsBOUNDED COUNTEREXAMPLES / RUST CPU

Find the point that breaks a claim.

Declare a comparison, choose a discrete grid and look for a witness. See which cells were visited, where a violation was returned and why silence is never a proof.

scan_counterexampleTry the real call
Concept artwork · not calculation evidence
01 / UNDERSTAND THE METHOD

A grid. A bound. One useful witness.

INPUT PREVIEW · RUN TO CALCULATE
Choose a case. Then bring it to life.

Preset buttons change the inputs. Calculation starts only when you ask.

Input preview. No numerical result yet.
THE COMPARISON TO TESTx ^ 2 ≤ 4tolerance 0
REQUESTED DISCRETE GRID7 cells
x=-3 · not visitedx=-2 · not visitedx=-1 · not visitedx=0 · not visitedx=1 · not visitedx=2 · not visitedx=3 · not visitedx: -3 → 3 (7 positions)
Not visitedVisited · not necessarily validReturned witness

The fixed scan varies the last variable fastest. This diagram displays the returned visit count and witnesses; it neither evaluates the expression nor invents values for other cells.

02 / ASK THE ACTUAL TOOL

Make it your experiment.

Complete tool arguments

Arrays, coordinates and nested contracts remain editable here. Units and limits are checked by the real tool.

Runs only when you press the button. Input edits discard the previous displayed result. Public compute limits apply.

KNOW WHAT THE RESULT MEANS

Useful evidence needs boundaries.

  • The scan uses finite Float64 evaluations and a numerical comparison guard, not interval arithmetic or a certified symbolic proof.
  • Absence of a witness covers only evaluated cells. Unvisited positions, values between grid cells and other variable ranges remain outside the observation.
  • Undefined expressions or comparisons too close to classify can make the result inconclusive. Such cells are never silently counted as passing.
  • The grid illustration uses requested coordinates, the returned visit count and returned witnesses. It does not invent function values or evaluate the expression in the browser.
  • The tool is directly callable by MCP. It has no approved planner adapter and does not replace a domain-specific stress test.