|
| 1 | +# Company and Product Map |
| 2 | + |
| 3 | +RQM Technologies develops software and API-first capabilities for quantum workflow engineering, with theory-informed methods grounded in quaternionic and SU(2) geometry. |
| 4 | + |
| 5 | +This documentation site focuses on **what is currently documented for production or beta integration**, while keeping research and planned interfaces clearly labeled. |
| 6 | + |
| 7 | +--- |
| 8 | + |
| 9 | +## How the pieces relate |
| 10 | + |
| 11 | +```text |
| 12 | +RQM Technologies (company) |
| 13 | + ├─ RQM Platform (documentation and integration surface) |
| 14 | + │ ├─ rqm-api (service boundary) |
| 15 | + │ ├─ rqm-circuits (public circuit boundary) |
| 16 | + │ ├─ rqm-compiler (internal optimization engine) |
| 17 | + │ ├─ execution bridges (qiskit / braket / pennylane) |
| 18 | + │ └─ rqm-studio (workflow product layer) |
| 19 | + └─ Research streams (theory notes, drafts, and planned interfaces) |
| 20 | +``` |
| 21 | + |
| 22 | +--- |
| 23 | + |
| 24 | +## Product and platform roles |
| 25 | + |
| 26 | +| Layer / Product | Current role in this docs site | Audience | |
| 27 | +|---|---|---| |
| 28 | +| **RQM Technologies** | Company umbrella for platform, product, and research efforts | Partners, evaluators, contributors | |
| 29 | +| **RQM Platform** | Core integration model and boundary architecture | Developers, coding agents | |
| 30 | +| **RQM Studio** | Browser workflow layer built on API services | Product users and workflow builders | |
| 31 | +| **rqm-api** | Public service boundary for validate/analyze/optimize/execution and account-linked flows | Integrators, backend/app developers | |
| 32 | +| **rqm-circuits** | Canonical public circuit schema and interchange boundary | SDK and API consumers | |
| 33 | +| **rqm-compiler** | Internal optimization/canonicalization engine (`u1q` internal) | Compiler engineers | |
| 34 | +| **Execution bridges** | Provider-specific lowering/routing surfaces | Teams integrating Qiskit, Braket, PennyLane | |
| 35 | +| **Theory / research notes** | Conceptual grounding and in-progress research narrative | Researchers and technical evaluators | |
| 36 | + |
| 37 | +--- |
| 38 | + |
| 39 | +## Documentation status model |
| 40 | + |
| 41 | +Use this model to interpret claims consistently: |
| 42 | + |
| 43 | +- **Production**: documented behavior intended for current integration. |
| 44 | +- **Beta**: documented, capability-gated behavior requiring explicit checks. |
| 45 | +- **Research**: conceptual or draft material; not a runtime contract. |
| 46 | +- **Planned/Proposed**: future-facing documentation, not available capability. |
| 47 | + |
| 48 | +If a page discusses research or planned material, treat it as non-contractual unless a production API surface explicitly documents availability. |
| 49 | + |
| 50 | +--- |
| 51 | + |
| 52 | +## Where to start |
| 53 | + |
| 54 | +- New to the platform: [Platform Overview](platform/overview.md) |
| 55 | +- Building integrations: [Getting Started / Quickstart](getting-started/quickstart.md) |
| 56 | +- Implementing with an agent: [Agent Portal](agents/index.md) |
| 57 | +- Evaluating trust and claims posture: [Verification / Trust](products/verification-trust.md) |
| 58 | +- Reading conceptual background: [Concepts](concepts/quaternion-intuition.md) |
| 59 | +- Reading current draft research: [QCE 2026 paper draft](research/qce2026-u1q-paper.md) |
0 commit comments