Exact

Exact Union RegExp

Repository files (latest commit first)

Filename	Latest commit message	Latest commit date
Transaction Science 7d0c795f63 WAI Quantum: wasmQ envelopes and qudit jobs on the job service and both MCP servers ... Until now a wasmQ envelope ran only from the command line and a qudit job only from the engine and the command line; the service and the MCP servers could verify a wasmQ job and run neither. - The job service runs both as jobs (src/hybrid.rs): POST /v1/wasmq (the envelope's bytes, {"envelope_base64"} or {"example"}; GET /v1/wasmq/examples) and POST /v1/qudit, each admitted in the order of what each step costs, opened or read and planned in a reading child (a refusal keeps its code, W001-W017 or J090-J092), queued within the client's and the service's limits, run in a worker (wasmQ on the native engine), kept in the store across a restart (the envelope under the digest its receipt binds) and sealed with the service's key; each waits as POST /v1/run does. The job's request is what the receipt binds: the contract and the envelope's digest, or the qudit request. The service's limits refuse, never truncate, and say so: an envelope past 786,432 bytes or whose run asks more than 2^38 of the profile's operations (quantum-wasmq §4.8) is refused J031 before it is queued, naming `wai-quantum run`; one past a job's memory is refused as any job is; a worker past its memory or the job's time is stopped and the job fails saying which, nothing sealed. A fault the envelope's own budgets cause is sealed. A wasmQ/2 run's energy.run is the worker's figure, read as every job's (the process's CPU energy on macOS, the packages' over its window on Linux), or the unmetered form with the reason. - MCP: run_wasmq (wai_wasmq::tool) and run_qudit (engine::qudit::tools) on both servers. The command line's runs a wasmQ/2 envelope in a process of its own and reads its energy as `wai-quantum run` does; the service's runs each as a job, output schema service-tools.v1.json#/$defs/hybrid_job, and get_quantum_job states such a job's verdict from what it holds. docs/local-mcp.json, docs/service-mcp.json, llms.txt, llms-full.txt and the skill's tools.md regenerated (WAI_QUANTUM_BLESS=1). - wai-wasmq: examples (seven conformance envelopes, byte for byte, a repo test holds them to the set), asks (a run's work and memory from the bundle alone), tool, and run::seal_for (sealing from the request a receipt binds). - Schemas: wasmq.v1.json; job.v1.json's request and result take a wasmQ run's and a qudit job's. Specs: quantum-wasmq §7 and §11.9, quantum-sim §9.10. Tested on the build hosts (Linux x86_64 Framework; the service's hybrid tests also on macOS arm64): wai-wasmq all tests and clippy -D warnings; wai-quantum --features full engine::schema:: engine::qudit:: quantum_qudit:: (36 passed) and the qudit workflow's pin (26 passed, unchanged); the service's mcp::, hybrid::, discovery::, offload:: unit tests and tests/hybrid.rs (4: both kinds over HTTP and MCP, each verified and reproduced, the four limits, the energy) and clippy -D warnings; wai-quantum-cli's whole suite, its MCP stdio test of both kinds among it. Co-Authored-By: Claude Opus 5.5 <[email protected]>		2026-11-10 18:55:11 -05:00
..
wai-quantum	WAI Quantum: wasmQ envelopes and qudit jobs on the job service and both MCP servers	2026-11-10 18:55:11 -05:00