resonant-quantum-mechanics9.24 KB
View saved version →
---
name: resonant-quantum-mechanics
description: Use when a user needs OpenQASM 3 validation or conservative repair, circuit equivalence or preservation checks, or supported local simulation from supplied circuit artifacts. Also use for eligible account-authorized Amazon Braket hardware preparation, quoted execution and original-result recovery; never claim hardware evidence from software analysis.
---
Use the `resonant-quantum-mechanics` MCP server at `https://jobs.rqmtechnologies.com/mcp/plugins/quantum` with `product: quantum` for this workflow. Respect the user's chosen provider; a general explanation without an artifact or engineering decision need not call these tools.
For hardware requests, use the hardware workflow below instead of the software-job selection steps. Never substitute a simulator or a Bell demo for a requested hardware workload.
On onboarding, explain the supported tasks and ask which artifact and decision the user has in mind. Discovery is sufficient to get started; installation or onboarding never authorizes execution.
1. Identify the artifact and desired decision. Identify the circuit source or supported artifact format, the intended validation, repair, comparison or simulation decision, and any supplied reference circuit. Ask for missing phase conventions, repair permissions, simulation settings and tolerances required by the selected schema. For repair or optimization, keep the original artifact; release a candidate only when the completed result explicitly validates the required preservation checks. Unsupported equivalence is not proof of equivalence.
2. Search with `search_buyer_jobs` using the user's natural task wording and this product scope; use `list_buyer_jobs` to inspect alternatives when needed. Compare the returned `use_when`, `do_not_use_when`, accepted formats, input schema, examples, readiness and limitations. Select only a supported match; explain unsupported or empty results without switching products. Catalog examples illustrate shape, not the user's measurements. For any later execution, select the matching separately exposed named operation from the current tool definitions, such as `quantum_openqasm3_preflight_v1`, `quantum_openqasm3_repair_v1` or `quantum_supported_circuit_equivalence_v1`. Confirm that its description and complete input schema match the intended service. Do not infer tool names by transforming a service ID, use an arbitrary capability selector, or route work through a generic executor. If no applicable named tool is exposed, explain the limitation and stop before execution.
3. Collect every missing measurement, unit, convention and tolerance required by the selected contract and named tool. Construct arguments exactly from that named tool's exposed input schema and the user's supplied data, including any request envelope it actually declares. Do not invent values, copy example measurements or add undeclared fields. Show the chosen task, exact inputs and limitations before seeking execution approval.
4. Require actual service readiness and valid owner-saved spending-policy evidence for this principal and product, plus explicit approval for these inputs and a finite maximum total price. OAuth sign-in, a subscription grant and `get_account_balance` alone do not establish policy readiness or spending authority. Scopes are `jobs.read`, `jobs.run`, `balance.read`. If the available tools cannot establish policy/readiness, say it is unverified and stop before execution; do not invent a readiness tool or probe by spending. Never select a policy, create a budget, grant access or fund the account. Stop on absent/expired policy, insufficient balance, exhausted budget, disabled purchases or unavailable dependencies.
5. For an approved new job, invoke only the matching separately exposed named Quantum operation, using its complete input schema. The operation binds its scientific service; do not choose a different service through an arbitrary capability ID or generic reque
Preview of the first 4,000 characters. Read full instructions →
