The open provider protocol gains §11: a device whose describe offers `landscape`
takes the job form of wai.quantum.landscape/1 itself (`{"op", "request"}`) in
estimate and submit, states the job's operations and memory as the extension counts
them, and answers the extension's own answer from result; a request the reader
refuses is `refused` with its sentence and line. No second job form: the client
checks the answer and seals it, naming the provider, its job and its cost.
quantum-landscape §5.4 gives thirteen numbered rules a verifier holds a sealed
answer to from the job alone (the member's id, class, kernels, parity, capacity
and floor, demotion and audit; the program's digest, the seed, the plan, the state's
hash, the replay digest, the priced joules, the verdict against the truth; a
replay's lines, the rows; a provider's members). A job that breaks one is the new
§8.4 reason `landscape_form` (engine::landscape); `wai-quantum verify` also reads the
program and gives an answer whose energy or plan is not the program's as not valid.
- wai-quantum-qpu: `landscape` (plan, run, check, seal); the reference provider
takes landscape jobs on the extension's reference (`--no-landscape`, `--qubits 0`);
the checker holds a provider to the new `landscape` vectors (ten messages, refusals
among them, six jobs with the reference's counts and bits pinned); the schema.
- wai-quantum: `landscape <op> --provider NAME [--dry-run] [--yes]`; verify prints the
form and the program's reading; MCP `run_landscape`, `landscape_estimate` and
`run_landscape_on_provider`.
- the job service: POST /v1/landscape/{run,sweep,compare,replay}, sealed with its key
in a reading child within its bounds, a request naming a provider refused (J002);
MCP `run_landscape`.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
a1837f01f9