Production QPU provider adapter boundary

Purpose and scope

Defines server-side trust, cost and receipt boundaries required for a real QPU provider. A local simulator adapter or synthetic provider test is not hardware-execution evidence.

Core design rules

• The adapter associates validated compiled output, a frozen target snapshot and one provider job identity.
• Credentials stay on the server; tenant, account and region isolation are explicit.
• Quota, cost, retry, cancellation and immutable hardware receipts have separate contracts.

Example from the original

This example illustrates the design recorded in the original. It is not by itself a claim of executable or stable support; check required options and the current version.

discoverTargets(binding) -> target snapshot
reserve(request, tenant) -> local reservation
submit(reservation, compiled carrier) -> provider correlation
poll(correlation) -> mapped provider state
cancel(correlation) -> mapped cancellation state
fetchReceipt(correlation) -> retained immutable receipt

Limits and interpretation

• The document selects no vendor, account or region and creates no real adapter or network request.
• Hardware readiness additionally requires actual provider evidence and the necessary external decisions.

Status and implementation boundary

The source is proposed. Do not advertise this boundary as real QPU access before implementation approval and provider/account/region decisions are complete.