RQM Platform¶
Agent-ready quantum software for validating, optimizing, and routing quantum circuits through tooling that understands quantum-state structure.
Do not learn the whole theory first. Enter through the problem you already have.
What are you trying to improve?¶
1) I optimize quantum circuits¶
Circuits are too large, too deep, or hard to reason about. Start by validating circuits, running optimization, and comparing before/after metrics such as gate count and depth where supported.
2) I build with Qiskit, Braket, PennyLane, or other SDKs¶
Use RQM as an optimization and routing layer around your existing SDK workflow instead of replacing your stack. RQM keeps quantum-state structure and SU(2) relationships visible for compiler diagnostics.
3) I am building with agents¶
Use machine-readable docs, prompts, contract tests, and recipes that AI coding assistants can execute against.
4) I evaluate, fund, or partner with advanced technology¶
See what is production, what is measured, and what remains research. Start from architecture and verification/trust boundaries.
5) I want the theory¶
Explore quaternionic/SU(2)/spinor geometry after choosing a practical entry path. Theory and research are non-contractual unless shipped in documented APIs.
The RQM connection model¶
RQM should be easy to enter from different user contexts. Quantum developers, SDK users, agents, evaluators, and researchers should not all be forced through the same front door.
This homepage is organized around practical connection points first: validate, optimize, integrate, and verify. Theory remains available, but downstream from implementation paths.
Architecture flow¶
Studio / SDK / Agent → rqm-api → rqm-circuits → rqm-compiler → execution bridges
Start by role¶
| Role | Recommended first door | Start here |
|---|---|---|
| Quantum Developer | 1) Optimize circuits | Optimization API, Quickstart, Optimization Engine |
| SDK Integrator | 2) Build with existing SDKs | Execution Bridges, Execution Workflows, Execution API |
| Coding Agent Builder | 3) Build with agents | Agent Portal, llms.txt, Contract Tests |
| Evaluator / Partner | 4) Evaluate or partner | Company + Product Map, Platform Architecture, Verification / Trust |
| Researcher | 5) Understand theory | Quaternion Intuition, SU(2) Geometry, QCE 2026 paper draft |
Documentation posture¶
Use documentation by maturity level:
- Production/Beta pages: implementation surfaces for real integrations, with documented API and boundary behavior.
- Research/Planned pages: non-contractual references unless and until behavior is shipped in documented API surfaces.
- When in doubt: confirm scope via Company + Product Map and API/product pages tied to your selected door.