Verify the right claim

Understand

Schema validity means the supplied data fits the supported contract. Energy equivalence means the source expression and converted energies agree within the reported numerical tolerance and validation scope. Neither statement alone proves an optimal domain answer.

Small compiled instances may receive exhaustive energy checks. Larger instances report a more limited validation scope. Read each native check, including not-checked statuses; never infer that every model was exhaustively solved.

Feasibility labels describe what was established for that family and instance. A successful compilation can still report unknown feasibility. Python SDK checks are not run inside this browser; the exported verification script must be run separately.

When a compiled QUBO is imported into Custom QUBO Modeler, its energy can be checked and executed within the existing limit. That is QUBO verification, not domain verification. Importing does not execute. A sampled answer, a feasible answer and a proven optimum are distinct claims.

Visualize

After explicit compilation, inspect validation checks with their native status and detail. No green success label replaces the per-check evidence.

Experiment

Compile Scheduling and TSP, then compare their feasibility evidence and exhaustive assignment counts. Find the SDK check marked not-checked and explain what must be done outside the browser.

Return to the example controls