Blocks and Inspector

A visual block is useful because it is readable. The inspector is useful because it is exact. Use both together.

When a user clicks a block, the inspector shows the fields and diagnostics needed to understand or change that part of the workflow.

Use properties for parameters, labels, target qubits, notes, and tags. This keeps the visual canvas clean while preserving precise configuration.

If a block participates in generated code, treat the property state as source-affecting. Review the code tab after meaningful edits.

Diagnostics help users catch invalid, incomplete, or risky block state before a provider route or run.

A clean workflow is easier to teach, easier to review, and easier to reproduce from evidence.

A visual block is useful because it is readable. The inspector is useful because it is exact. Use both together.

When a user clicks a block, the inspector shows the fields and diagnostics needed to understand or change that part of the workflow.

Use properties for parameters, labels, target qubits, notes, and tags. This keeps the visual canvas clean while preserving precise configuration.

If a block participates in generated code, treat the property state as source-affecting. Review the code tab after meaningful edits.

Diagnostics help users catch invalid, incomplete, or risky block state before a provider route or run.

A clean workflow is easier to teach, easier to review, and easier to reproduce from evidence.

Purpose