wai-quantum 0.4.3: metered runs, placement by a run's energy, and a fabric that falls back #226

Merged

dcharlot merged 4 commits from wai-quantum-fabric-energy into main 2026-10-12 19:59:15 -04:00

Conversation 0 Commits 4 Files changed 13 +1479 -49

2026-10-12

Transaction Science

wai-quantum fabric: the review of the energy stage, fixed ...

An independent review found no wrong figure, pairing or fallback in the
arithmetic; it found four things the code did not hold.

- A receipt's member was whatever Member the caller paired with a runner:
  nothing compared them, so a member paired with another adapter's runner gave a
  signed, verifying receipt for work it did not do. A Runner now states the
  member it is (member_id), and Fabric::run refuses a pairing whose ids differ
  as a defect, before anything runs.
- "Figures on both members or on neither" was documented, not held: a
  calibration that earns no figure on one member (its readings under the
  resolution floor, say) left the other placed first whatever it cost. place is
  unchanged; place_for and Fabric now read figures on only some candidates as
  figures on none.
- Tests: the assertion that only placeable candidates are predicted held for
  any implementation, and is now a closure that panics on an unplaceable one
  over a list that holds two; a runner that hands back a refused label, or a
  label with no figure, is sealed as unmetered; the device test runs the tile
  implementation metered and on the fabric.
- The member's detail said a window "covers device work only"; it also holds
  the host's waits and copies between submissions, and says so.

Also: a calibration whose uncertainty no longer fits its field once the rounding
is added earns no figure rather than a capped one; ready() drives Fabric::run
natively without an executor; &R is a Runner and &mut M a RunMeter.

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

1665baee8f

• View at this point in history

2026-10-12 15:38:07 -04:00

Transaction Science

Merge remote-tracking branch 'origin/main' into wai-quantum-fabric-energy

136b16f0f2

• View at this point in history

2026-10-12 15:29:40 -04:00

Transaction Science

wai-quantum 0.4.3: metered runs, placement by run, and the fabric wrapper ...

Additive release of Stage 6. The CHANGELOG gains a 0.4.3 section above 0.4.2; the
version changes in Cargo.toml and in the version line of the six lockfiles that
resolve wai-quantum. The quantum-wasip2 job requires each new fabric test by name.
The place_for test now also drops the CPU's prediction, so a missing prediction
read as zero would place the CPU where place places the GPU, and fail.

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

b3dae20921

• View at this point in history

2026-10-12 05:25:03 -04:00

Transaction Science

wai-quantum fabric: run meters, metered calibration, place_for, and the Fabric wrapper ...

Stage 6 of the WebGPU member plan (energy, and placement that can choose the GPU).

- quantum_fabric: the member-neutral RunMeter trait (no meter ships in the crate);
  a reading reaches a result only when check_label accepts it, every start is
  matched by one stop, and a refused run's reading is discarded. EnergyCalibration
  turns metered runs into a KernelEntry figure (nJ per pair-update, rounded up,
  the runs' class with the rounding folded into its uncertainty), or no figure at
  all; detect_local_metered gives the CPU reference its figure. place_for places
  one run by a caller's picojoule model when every candidate has a prediction,
  else as place. Fabric runs a circuit on the placed member, falls back down the
  placement order on TooWide, OutOfRange, Memory, Timeout or Device, and seals the
  receipt with the member that produced the result, the refusals beside it.
- quantum_fabric_webgpu: simulate_metered brackets a run from its first submission
  to its last readback (device work only; detail says so), member_metered
  certifies and calibrates in one pass, the member is a Runner for its own
  implementation, and WebGpuError maps onto MemberError.
- Tests: CPU-side tests with synthetic meters, figures, models and refusing
  members; device test g13 (metered runs, a metered calibration, and the fabric
  falling back from a member held to three qubits); the member script expects 14
  tests and a fabric line per declared adapter.

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

852cd42e80

• View at this point in history

2026-10-12 05:08:11 -04:00