Build with the QuantumSoftware stack.
Start with the N/M language, explore runnable examples in the playground, and follow the research notes behind the platform.
One entry point, three evidence paths
Use the language reference to understand contracts, the Playground to inspect local execution, and the research record to keep methods and limits attached to results.
- Documented surfaces
- Language · Playground · Research
- Reading paths
- 3 connected starting points
- Execution boundary
- Local-first, reproducible examples
01 / Documentation map
Choose the artifact you need next
Each path answers a different question: what the language guarantees, what the current runtime produces, or how an experiment should be handed off for review.
Language reference
N/M Language
Read the language overview, core semantics, examples, and hardware-targeted programming model.
What you will find
Versioned syntax, capability levels, diagnostics, and implementation boundaries
Runnable workspace
Interactive Playground
Run small quantum programs, inspect measurements, and experiment with the current simulator.
What you will find
Local simulation, traces, measurements, exports, and bounded analysis
Evidence record
Research Resources
Browse research areas, publications, and collaboration topics across the platform.
What you will find
Methods, assumptions, reproducibility notes, and collaboration context
02 / Runnable start
Quick start
After installing the public CLI package, create a starter, run it in the simulator, then transpile it for a supported target profile.
Core, CLI, MCP and Language Server packages are available on npm. Use next for the preview channel or pin the documented package version. The N/M language and VS Code extension versions are tracked separately.
$ nm init main.nm$ nm run main.nm$ nm transpile main.nm --target superconducting