Quantum access has to follow the experiment

A research pilot should begin with the experiment it needs to answer. Local simulation can expose circuit mistakes, establish a baseline and produce an early record. A hardware run is justified when the question depends on device behaviour and the team can name its backend, permissions, expected cost, shot budget and review path.

This distinction matters for QFlow Studio's university and research use cases. The product can help make a design, generated code and run evidence understandable together, while the underlying provider remains responsible for its account, allocation, pricing and device operation.

Recent conversations with quantum-platform teams have focused on the practical route from a small teaching or research pilot to repeatable usage. We are comparing institution-managed credentials, separately funded provider consumption and, only where a provider explicitly agrees, a defined usage allowance in a future QFlow package. These are commercial and operating models under discussion, not announced entitlements.

The evaluation record should remain the same whichever route is chosen: the question, circuit and code, simulator baseline, selected execution context, actual job identity, observed result and a note about uncertainty. That lets a reviewer judge the work without mistaking a provider connection for a scientific result.

Provider discussions have not produced a bundled hardware allowance, exclusive access, certified integration or jointly launched pilot. QFlow's existing public and credentialed routes retain their own status labels. The next step is a bounded pilot design with clear account ownership, cost responsibility and evidence requirements before any broader access model is offered.