Quantum Problem Compiler · Learn

Interpret documented English

Understand the bounded template grammar and review every interpretation.

Understand

The English interpreter is deterministic and local. It recognizes documented patterns; it is not a general-purpose language model and does not understand arbitrary prose. Unrecognized or ambiguous clauses must be resolved before native review.

For TSP, list cities and one complete distance row per city in that order. For routing, columns follow the depot then customer lines. Diagonals must be zero and distances exactly symmetric.

For scheduling, machine numbers start at 0 and operation lines define the order within each job. Use integer durations and a horizon from 1 to 2,048. A recognized sentence is only an interpretation: native validation still has to accept its data.

Visualize

Edit the template to see the existing interpreter produce either canonical input or actionable diagnostics. The same interpreter powers Describe Your Problem in the full Compiler.

Loading the local example explorer…

Experiment

Remove the Vehicle capacity line from Routing and inspect the missing-data diagnostic. Restore the template. Add an unsupported time-window sentence and see why it cannot be silently accepted.

Return to the example controls

Apply

Start with a documented template, replace its values, and review the objective and constraints. Use canonical JSON when you need an explicit structured input.

Open Quantum Problem Compiler

Check your understanding

Does recognizing an English template prove the data is valid?