Runtime

The execution runtime layers configuration, plans, strategies, diagnostics and introspection on top of the backend contract. Full API details live in the generated reference; the links below jump straight to the relevant module.

• ExecutionRuntime — coordinates preparation, compilation, submission and collection, enriching results with metadata and traces.

• RuntimeConfig — frozen, JSON-safe defaults (backend, registry, default target, history cap, optimization level); passed as config=... or derived via configure().

• ExecutionPlan — declarative description of what to run (see Execution Plan).

• ExecutionStrategy — DIRECT / COMPILED / BATCH / PARAMETER_SWEEP / HYBRID dispatch and pluggable handlers (STRATEGY_HANDLERS, register_custom_strategy).

• ExecutionTrace — per-execution lifecycle record.

• Stage-tagged errors in microquantum.runtime.errors — all subclasses of ExecutionError (which subclasses ValueError, so existing except ValueError code keeps working): PlanningError, CompilationError, RuntimeDispatchError and BackendExecutionError.

• Introspection — runtime_info() returns a RuntimeInfo snapshot (version, Python / NumPy, strategies, live backend capability summaries, default backend).

• Module-level convenience entry points execute(), submit(), execute_batch, submit_batch, execute_records, run_parameter_sweep, run_hybrid, run_experiment route through the shared default_runtime.

See Runtime for the narrative guide, and Command Line for the microquantum developer command line.

Generated reference (by module)