wai-quantum: energy-landscape jobs, a classical emulator of the settling model, and the extension wai.quantum.landscape/1 #664

Merged

dcharlot merged 10 commits from wai/quantum-landscape-emulator into main 2026-11-06 14:49:33 -05:00

Conversation 0 Commits 10 Files changed 71 +32062 -11

dcharlot commented 2026-11-06 02:25:29 -05:00

Owner

Copy link

A job of this kind gives no circuit. A program in epuML states an energy over variables of three states, and the answer is a state of low energy. This adds that job to the engine, the command line and the browser build, with a classical emulator of the settling model as its reference, and an open extension that says how a GPU or an FPGA board runs the same job later. Nothing here is a quantum effect, and every answer says so.

What is here

• quantum_landscape in wai-quantum (in quantum_engine and full, no new dependency): the reader, a deterministic kernel in whole numbers, a sampling kernel of one draw between two cut points, the exhaustive truth up to 16 variables, the answer, the joules, classical methods and the table.
• wai-quantum landscape: run, sweep, compare, replay, examples, table, instance, call, corpus, vectors, trial-assignment.
• QuantumEngine.landscape and landscape_answer in wai-web, and wai-web/demo/landscape.html.
• The extension wai.quantum.landscape/1 (extensions/quantum-landscape.md): the job, the answer, how joules are stated, and the seam (quantum_landscape::member::Member): a member runs the kernels, and the reader, the energy, the checks, the verdict, the digest and the seal stay on the host and do not trust it. An answer names what ran it and how far that member's kernel is held to the reference. The CPU reference is the only member implemented.
• quantum-conformance/landscape/: the vectors a member is held to, the results, a stated result and reproduce.sh.
• .github/workflows/wai-quantum-landscape.yml, with narrow paths, and the pins of wai-web-wasm.yml raised by one test each.

What keeps it honest

• Each answer carries a label that says what kind of run it is, word for word.
• Joules are priced, and no line calls a run's joules measured. Temperature 0 and sampling have their own rates, each with its source, and the small-job line says how much of the board's own draw the rate leaves out. The figure's class is ModelBased and describes the board its rate was read from; the future chip's is Estimator.
• Eight of the fourteen worked examples fail on purpose, and are reported as failures. Every lowest arrangement is graded against the problem's own check, so a landscape that does not express its problem fails even where a run's answer passes by luck.
• The equal-budget table is published as it came out. Against the best of simulated annealing, tabu search and greedy descent, the sampling mode at the default start is ahead in 2 rows of 68, by one run of a hundred each, tied in 45 and behind in 21. Simulated annealing leads at the larger sizes.
• The default start is stated, with the held-out data that shows a start at the largest row of couplings is too hot, and the rows where the default is beaten by a start of 1.

Checked

host	what	result
Linux x86-64	--features full --lib, of which the module	1,244 passed, 68 of them the module's
	landscape_conformance; the command line (78 in its binary, 2 of them the verb's); wai-web native	6; 78; 30
	feature sets under -D warnings	clean
	wasm32-wasip2 under wasmtime 50.0.1, debug	67 passed
	reproduce.sh	every value
Linux arm64	the module, release; the pinned bits, debug; landscape_conformance	68; 2; 6
	reproduce.sh	every value, the same bytes
macOS arm64	the module, release; the pinned bits, debug; landscape_conformance	68; 2; 6
	wai-web wasm32 under Node	22 passed
	reproduce.sh, with the browser build	every value, the same bytes
	browser build against the command line, 2,000 seeds, Node	700 answers the same bytes, 0 different, 104,000 seeded runs
	the page in Chrome, 500 seeds	61 checks passed; 84 of 84 answers the same bytes, 19,500 seeded runs

docs/landscape.md passes check_docs.py, its Rust snippet included. The repository's name, prose, vanity-metric, spec-reference, tests-in-CI, orphan-source, wasmtime-pin, concurrency and lockfile checks pass. The new tests, the workflow and the results were all run on these hosts; this forge's CI has not run them yet.

For whoever merges

• #644 (every wai.quantum string accounted for) reads wai.quantum.landscape/settle and wai.quantum.landscape/sample as kernels. Whichever of the two lands second adds them to the registry's kernel labels, as wai.quantum.sv/run is. wai.quantum.landscape/1 is a schema's name and needs no line.
• The code came from a private crate declared BSL-1.1 at d46e63d7b, and is relicensed Apache-2.0 by its copyright holder's decision of 2026-11-05 (wai-quantum/src/quantum_landscape/PROVENANCE.md).

🤖 Generated with Claude Code

A job of this kind gives no circuit. A program in epuML states an energy over variables of three states, and the answer is a state of low energy. This adds that job to the engine, the command line and the browser build, with a classical emulator of the settling model as its reference, and an open extension that says how a GPU or an FPGA board runs the same job later. Nothing here is a quantum effect, and every answer says so. ## What is here - **`quantum_landscape`** in `wai-quantum` (in `quantum_engine` and `full`, no new dependency): the reader, a deterministic kernel in whole numbers, a sampling kernel of one draw between two cut points, the exhaustive truth up to 16 variables, the answer, the joules, classical methods and the table. - **`wai-quantum landscape`**: `run`, `sweep`, `compare`, `replay`, `examples`, `table`, `instance`, `call`, `corpus`, `vectors`, `trial-assignment`. - **`QuantumEngine.landscape` and `landscape_answer`** in `wai-web`, and `wai-web/demo/landscape.html`. - **The extension `wai.quantum.landscape/1`** (`extensions/quantum-landscape.md`): the job, the answer, how joules are stated, and the seam (`quantum_landscape::member::Member`): a member runs the kernels, and the reader, the energy, the checks, the verdict, the digest and the seal stay on the host and do not trust it. An answer names what ran it and how far that member's kernel is held to the reference. The CPU reference is the only member implemented. - **`quantum-conformance/landscape/`**: the vectors a member is held to, the results, a stated result and `reproduce.sh`. - **`.github/workflows/wai-quantum-landscape.yml`**, with narrow paths, and the pins of `wai-web-wasm.yml` raised by one test each. ## What keeps it honest - Each answer carries a label that says what kind of run it is, word for word. - Joules are priced, and no line calls a run's joules measured. Temperature 0 and sampling have their own rates, each with its source, and the small-job line says how much of the board's own draw the rate leaves out. The figure's class is `ModelBased` and describes the board its rate was read from; the future chip's is `Estimator`. - Eight of the fourteen worked examples fail on purpose, and are reported as failures. Every lowest arrangement is graded against the problem's own check, so a landscape that does not express its problem fails even where a run's answer passes by luck. - The equal-budget table is published as it came out. Against the best of simulated annealing, tabu search and greedy descent, the sampling mode at the default start is ahead in 2 rows of 68, by one run of a hundred each, tied in 45 and behind in 21. Simulated annealing leads at the larger sizes. - The default start is stated, with the held-out data that shows a start at the largest row of couplings is too hot, and the rows where the default is beaten by a start of 1. ## Checked | host | what | result | |---|---|---| | Linux x86-64 | `--features full --lib`, of which the module | 1,244 passed, 68 of them the module's | | | `landscape_conformance`; the command line (78 in its binary, 2 of them the verb's); `wai-web` native | 6; 78; 30 | | | feature sets under `-D warnings` | clean | | | `wasm32-wasip2` under wasmtime 50.0.1, debug | 67 passed | | | `reproduce.sh` | every value | | Linux arm64 | the module, release; the pinned bits, debug; `landscape_conformance` | 68; 2; 6 | | | `reproduce.sh` | every value, the same bytes | | macOS arm64 | the module, release; the pinned bits, debug; `landscape_conformance` | 68; 2; 6 | | | `wai-web` wasm32 under Node | 22 passed | | | `reproduce.sh`, with the browser build | every value, the same bytes | | | browser build against the command line, 2,000 seeds, Node | 700 answers the same bytes, 0 different, 104,000 seeded runs | | | the page in Chrome, 500 seeds | 61 checks passed; 84 of 84 answers the same bytes, 19,500 seeded runs | `docs/landscape.md` passes `check_docs.py`, its Rust snippet included. The repository's name, prose, vanity-metric, spec-reference, tests-in-CI, orphan-source, wasmtime-pin, concurrency and lockfile checks pass. The new tests, the workflow and the results were all run on these hosts; this forge's CI has not run them yet. ## For whoever merges - **#644** (every `wai.quantum` string accounted for) reads `wai.quantum.landscape/settle` and `wai.quantum.landscape/sample` as kernels. Whichever of the two lands second adds them to the registry's kernel labels, as `wai.quantum.sv/run` is. `wai.quantum.landscape/1` is a schema's name and needs no line. - The code came from a private crate declared `BSL-1.1` at `d46e63d7b`, and is relicensed `Apache-2.0` by its copyright holder's decision of 2026-11-05 (`wai-quantum/src/quantum_landscape/PROVENANCE.md`). 🤖 Generated with [Claude Code](https://claude.com/claude-code)

dcharlot added 5 commits 2026-11-06 02:25:29 -05:00

wai-quantum: quantum_landscape, energy-landscape jobs on a classical emulator ... f7078696d0

A program in epuML states an energy over variables of three states; the module
reads it, runs it on the settling model's two kernels (a deterministic sweep in
whole numbers, a sampling sweep of one draw between two cut points, both the same
bits on every platform), checks every arrangement up to 16 variables, grades each
lowest one against the problem's own check, prices the joules at rates whose
sources are named, and runs simulated annealing, tabu search and greedy descent
on the same instance at the same budget. A member trait is the seam a GPU or an
FPGA board runs behind; the CPU reference is the only member here.

The feature is in quantum_engine and full, with no new dependency, and wai
re-exports it. The answer's schema is wai.quantum.landscape/1, and the conformance
set a member is held to is quantum-conformance/landscape/vectors.json, which a
test holds to the code.

The code came from a private crate declared BSL-1.1 at d46e63d7b, and is
relicensed Apache-2.0 by its copyright holder's decision of 2026-11-05
(src/quantum_landscape/PROVENANCE.md).

Co-Authored-By: Claude Opus 5.5 <[email protected]>

wai-quantum-cli: wai-quantum landscape ... e357f496ae

run, sweep, compare, replay, examples, table, instance, call, corpus, vectors and
trial-assignment. A job that ran exits 0 whatever its verdict; a program that
cannot run exits 1 with one plain sentence and its line. The help is in the
zh-CN locale, and docs/llms-full.txt is regenerated.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

wai-web: energy-landscape jobs in a page ... cb28655cd9

QuantumEngine.landscape seals an answer with the page's key and
landscape_answer gives the unsealed bytes the command line's `landscape call`
writes. A native test and a wasm32 test pin the worked examples' digest, and
wai-web-wasm.yml's counts rise by one each. demo/landscape.html is the page, and
two scripts compare its answers with the command line's, in Node and in Chrome.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

wai: the extension wai.quantum.landscape/1, its results and its workflow ... 699a016d80

extensions/quantum-landscape.md states the job, the answer, how joules are
stated (priced, never called measured, sampling at its own rate, what the rate
leaves out), and the seam a GPU member or an FPGA board runs behind, with each
answer naming what ran it and how far it is held to the reference.

quantum-conformance/landscape holds the equal-budget table, published as it came
out (simulated annealing leads on the larger instances), the starting-temperature
data behind the default, a trial outside the job form, the browser build's parity
record, a stated result and the script that checks it. The docs page, the READMEs,
the version policy, the changelog entry and wai-quantum-landscape.yml come with it.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

Merge main into wai/quantum-landscape-emulator ... 8368e3de6a

Co-Authored-By: Claude Opus 5.5 <[email protected]>

dcharlot added 1 commit 2026-11-06 02:35:21 -05:00

wai-quantum: the label names no product ... e84cf47863

"the planned e-QPU's settling model" becomes "the settling model of a planned
energy-based processor" in the label, the spec's quotation, the page and the
page's test; the rest stays word for word. The label is inside every answer, so
the digests over whole answers are pinned again: the corpus digests natively and
in wasm32, and the stated result's lines. The replay digests, the table and the
conformance set do not hold the label and do not change.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

dcharlot referenced this pull request from a commit 2026-11-06 03:49:39 -05:00

wai-quantum: bound every quantity a job can ask for, and check what a member claims

dcharlot referenced this pull request from a commit 2026-11-06 03:49:39 -05:00

wai: the extension states exactly what the code does

dcharlot added 3 commits 2026-11-06 03:49:39 -05:00

wai-quantum: bound every quantity a job can ask for, and check what a member claims ... eb0db88956

From the engine review of #664:

- A job is bounded before any of it runs, the same on every host: the program's
  length, `steps` (now at least 1) and `restarts`, the `#! check` lines and their
  items, the numbers in them, and the fields after pins and quantisation. The
  operations of the whole job (the n² rows, the exhaustive truth, every run and
  every seed of a replay) and the memory it can hold are counted first; chains go
  to a member a batch at a time, so a run's memory does not grow with its starts.
- Quantised weights and pins are held to 2^40, so the exhaustive truth cannot
  overflow; the most negative whole number no longer passes through abs().
- The grammar is ASCII and strict (no `+`, no exponent in a temperature, spaces
  and tabs only), and a temperature string has a grammar of its own; the module
  reads JSON numbers to the nearest double with its own feature.
- A member takes every sweep's temperature from the host. Every answer it returns
  is checked: a fixed point rests, a two-cycle has period 2, a bound was reached,
  the work and the draws are what the schedule comes to.
- A member's parity is found, not declared: bit-exact on the settle and chains
  vectors, statistical on a battery of workloads that catches a kernel moving
  coupled cells at once, ignoring its schedule, sampling the last sweep or using
  a wrong table. Only the host's own kernels are "reference".
- Sums of energies are taken in 128 bits; balance checks in 128 bits.
- The conformance set pins the exponential, the schedule, the cut points over a
  wide grid, chains with every start of a run, and requests for each rule.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

wai: the extension states exactly what the code does ... 55a86e72c0

From both reviews of #664: the limits and how operations and memory are counted;
the grammar; a pin's size; how weights are quantised; the plans, `minimize` above
temperature 0 among them; the state a two-cycle reports and what a settle's digest
holds; the schedule and the cut points to the operation; the exponential, in an
appendix; the host's checks of a member's answers; parity as found; the battery.
The joule line's 0.03 pJ is stated as what it is, a published 2014 figure for one
8-bit integer add, given for scale; the label says so in place of a modelled chip.
The provenance names the copyright holder that relicensed the code.

The page's refusals through Sweep and Compare reach the live status, the sweep
shows the board draw each priced figure leaves out, and the count under the
published table is of the rows it shows. reproduce.sh fails when the browser build
differs, skips a wasm-bindgen other than the lockfile's, and compares table.md and
the trial too. The workflow's paths take the command line's and the browser
crate's manifests and lockfiles, and its counts are the tests as they are.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

wai: the stated result restated, and the page reads the scale figure by its name ... f4575220b5

The label and the answer's joules changed, so the digests over whole answers
moved: the talks' lines, every example's lines and the corpus digest are stated
again, from runs of reproduce.sh on x86-64 Linux, arm64 Linux and macOS (with the
browser build), each giving every value. The page read the figure for scale by its
old name and could not show a run's card; the page check caught it, and now passes
77 of 77 with the browser build's answers the command line's bytes.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

dcharlot referenced this pull request 2026-11-06 08:21:14 -05:00

wai-quantum: energy-landscape jobs on a GPU, through WebGPU, CUDA and Metal, each member certified by the host #672

dcharlot referenced this pull request from a commit 2026-11-06 14:02:27 -05:00

Merge wai/quantum-landscape-emulator (#664) into wai/quantum-landscape-fpga: the host certifies the board, and the board runs any schedule

dcharlot referenced this pull request 2026-11-06 14:02:35 -05:00

wai-quantum-landscape-fpga: an FPGA board as an open reference member of wai.quantum.landscape/1 #677

dcharlot added 1 commit 2026-11-06 14:49:01 -05:00

Merge main into the emulator; say the schema list's new length is a change ... b5424f0aef

Main brings the CI fixes and the receipts work. The conformance README keeps
both sections. `wai breaking` reported engine::schema::FILES going from 24 to 25
entries unacknowledged, so the change entry now says so.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

dcharlot merged commit 3f8552c48c into main 2026-11-06 14:49:33 -05:00

dcharlot referenced this pull request from a commit 2026-11-06 14:49:35 -05:00

Merge pull request 'wai-quantum: energy-landscape jobs, a classical emulator of the settling model, and the extension wai.quantum.landscape/1' (#664) from wai/quantum-landscape-emulator into main

dcharlot referenced this pull request from a commit 2026-11-07 03:45:22 -05:00

Merge main into wai/quantum-landscape-fpga: #664 has landed

dcharlot referenced this pull request from a commit 2026-11-07 03:46:44 -05:00

Merge wai/quantum-landscape-emulator (#664) into wai/quantum-landscape-fpga: the label names no product

dcharlot referenced this pull request from a commit 2026-11-07 03:49:26 -05:00

wai-quantum-landscape-fpga: PROVENANCE names the copyright holder, Open Interface Engineering, Inc.

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

Transaction-Science/open-standards!664

No description provided.