wai-quantum: methods, passes, noise channels and formats behind traits, every built-in registered through them, a host's own components checked and marked #560

Merged

dcharlot merged 4 commits from wai/quantum-registration into main 2026-11-01 03:37:29 -05:00

Conversation 0 Commits 4 Files changed 42 +5909 -209

2026-10-31

Transaction Science

wai-quantum engine::refusal: J011 no longer names noise, which J061 now covers ...

Noise a method cannot take is refused with J061 since the registry, so J011's meaning stops listing
it and points there; the docs page's table, which a test holds to the code's, says the same.

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

4f901247c7

• View at this point in history

2026-10-31 23:30:48 -04:00

Transaction Science

wai-quantum docs: the example's commands as the registry workflow runs them ...

The docs check holds a block that cannot run here to the workflow named:
the example's test and run, with --locked, as wai-quantum-registry.yml
runs them.

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

223ed634bf

• View at this point in history

2026-10-31 23:30:48 -04:00

Transaction Science

wai-quantum-cli, wai-quantum-service: the engine's components listed on the command line, both MCP servers and the service ...

`wai-quantum components` (`--json` with each descriptor), the MCP tool
list_components on both servers (its answer tools.v1.json#/$defs/components),
and the service's GET /v1 and quantum_service_info list every method, pass,
noise channel and format with its version, origin and descriptor digest:
the built-ins alone, nothing loaded from a request. The tool lists' tests,
the smoke checks and the second schema checker take the new tool; the agent
docs are blessed from both servers; the command's summary is translated;
the READMEs and the changelog say what the extension points are.

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

022b02f58e

• View at this point in history

2026-10-31 23:30:48 -04:00

Transaction Science

wai-quantum engine::registry: methods, passes, noise channels and formats behind traits, the built-ins registered through them ...

Method, Pass, Channel and FrontEnd, and one registry the planner, the run,
the compile, the conversions and the verdict go through. Every built-in
registers through the same trait a host's own implements: the twelve
methods and the pulse simulator, the eight passes, the five channels and
the three formats. Registry::with_builtins() and register(...) are
explicit and stay in the process.

The engine checks what a registered component gives: a method's class and
the members the engine writes, a pass's output against its input on the
whole circuit by the ladder or a distance bound, a channel's Kraus
operators completely positive and trace preserving at each job's values,
a format's program reading. A result a registered component took part in
carries `components`, each identity (name, version, descriptor digest)
marked registered and certified false, sealed by its receipt; a result of
built-ins alone gives the bytes it gave, the eight pinned job digests
holding through any registry. Refusal codes J060 to J065. The example
examples/extension_points.rs, docs/extension-points.md, and the CI leg
wai-quantum-registry.yml.

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

56b47afae1

• View at this point in history

2026-10-31 23:30:48 -04:00