Look, I was digging through the docs again and this bit still stands out.
@quipnetwork ’s job path expects a classical pre-processing step before anything hits a quantum device. That step can shrink the instance, map it to the machine’s topology, and package the verification data, but it cannot invent the measurement. The quantum part still has to come from a real run, and the published result has to match the rule the job named. An annealer job and a gate-model job take different packages, so the handoff is not the same for both. I am reading this as a pipeline detail inside scheduling. It does not say which machine is free, and it is not a reason to submit, buy, or compare jobs.
(📷According to X rules, a paid partnership has been selected. It is not investment advice or a paid partnership.)