A multi-year partnership announced, and no agreement filed
7 min read
Anyone buying access to quantum computing through a large cloud vendor today is buying the announcement of a machine that is not yet running inside it. That fact sits in the filings of Quantinuum Inc. (NASDAQ: QNT, CIK 0002110105), a Delaware company that has been listed for only a few months: its first SEC filing is a DRS — a confidential draft registration statement — dated 17 February 2026; 47 filings have followed since. The latest, dated 11 August 2026, announces a multi-year partnership with Oracle. That is where the reading starts to diverge from the press release’s headline.
One 8-K, three points, and one that is missing
The document is a Form 8-K filed on 11 August 2026 (accession 0001628280-26-055699), signed by CFO Nitesh Sharan: an Item 2.02 with results for the quarter ended 30 June (Exhibit 99.1); an Item 7.01 — Regulation FD Disclosure stating, verbatim: “On August 11, 2026, the Company issued a press release announcing a multi-year strategic partnership with Oracle to accelerate hybrid quantum compute adoption on Oracle Cloud Infrastructure” (Exhibit 99.2); an Item 9.01 whose only exhibits are the two press releases and the XBRL cover page. On both Items the filing states, verbatim: “The information furnished pursuant to this Item … shall not be deemed ‘filed’ for purposes of Section 18 of the Securities Exchange Act of 1934” — the same furnished versus filed distinction we measured yesterday, and here it is not the story.
The story is an absence. There is no Item 1.01 in the 8-K — the item a company uses to disclose that it has Entry into a Material Definitive Agreement, the caption of the form itself outside the ordinary course of business, which requires filing the agreement as an exhibit. It is not there: no agreement attached, no amount, no term beyond the adjective “multi-year”. This is not an irregularity: it means Quantinuum did not treat the deal as a definitive, material agreement requiring a filing — for any of several possible reasons: not material, not definitive, ordinary course. For a buyer, though, the difference is enormous: of that multi-year partnership, the public has no text, no figure, no term and no exit terms.
Two superlatives, two footnotes
The release — Exhibit 99.2 — calls Helios “the most accurate commercial quantum computer in the world,” with a footnote reading, verbatim: “Based on two-qubit gate fidelity as of December 31, 2025.” The superlative rests on a single metric, measured more than seven months before the announcement.
The second superlative: “A single Helios system has an estimated power draw of less than one percent of the draw reported for leading supercomputers”. The footnote, verbatim: “According to Tchakoute, R.N., et al. (2026) Energy-Aware Computing in the Year 2026, leading supercomputers use 16 MW to 39 MW of energy, whereas a single Helios unit uses approximately 60 kW without an HVAC system.” The two sides of the comparison are not measured the same way: one figure is the “reported” draw of the other machines, the other is Helios’s draw without air conditioning. The release states this in the footnote: it does not hide it, it just puts it where almost no one reads.
A service that does not exist yet
The rest of the release is almost entirely in the future and conditional tense. “Oracle plans to preview its OCI quantum service in the coming months”. Customers “can expect to gain” managed, secure access; Helios “is anticipated to be able to integrate” seamlessly with existing OCI compute, networking, storage, identity and data services; the planned OCI quantum service “is expected to combine” Quantinuum’s development stack with support for open-source hybrid-programming frameworks. The service does not exist yet: it is announced as a preview, with no date given.
What is already done
Helios was commercially launched in November 2025: a third-generation, trapped-ion system on a QCCD architecture, 98 physical qubits, used in demonstrations with 48 logical qubits, an average two-qubit gate fidelity of 99.921% — above the commonly cited “three nines” threshold. It will be deployed inside a US OCI AI data centre, and will operate, verbatim, “on-premises within OCI’s infrastructure”. The statements come from Dr Rajeeb Hazra, President and CEO of Quantinuum, and Mahesh Thiagarajan, Executive Vice President of Oracle Cloud Infrastructure; the release also carries comments from Johannes Blaschke (Ellison Institute of Technology) and Heather West (IDC) — voices present in the text, with no corporate relationship to Oracle that we have verified.
The asymmetry of the filings
The terms of this deal can only be read in Quantinuum’s filings, because Quantinuum is the one obliged to file them — the same imbalance measured yesterday in another licence paid in shares. On Oracle’s public list of press releases (oracle.com/news), checked today, the latest one listed is dated 28 July 2026, and Quantinuum does not appear — that is not proof of absence, since the index is not updated in real time: we state it as such, without claiming Oracle has said nothing.
See the service · Talk to an engineer
What we do not know
We do not know the text of the agreement, its precise term, the figures involved, or the exit terms: the 8-K neither attaches nor describes them. We do not know when the OCI quantum service will be available: the release says “in the coming months”. We do not know whether the fidelity declared as of 31 December 2025 still holds today, nor how it compares with competitors now: we have no independent measurements and make none. There is nothing unlawful or suspicious here: announcing under Item 7.01 is legitimate and ordinary, and the footnotes are there, published. The value of this piece is the reading, not an accusation.
The question for the buyer
Anyone considering buying quantum access through a cloud vendor is buying, today: a machine that is not yet running, inside a data centre it does not control, through a service that has not launched, on the basis of an agreement with no public text — the same lesson taught by who ends up holding an authorisation obtained inside someone else’s perimeter. None of these four things is a problem in itself: it becomes one if it is not written anywhere in your contract. The questions the case makes concrete: which legal entity owes you the performance, and under what instrument; where the workload physically runs, and under what jurisdiction; what happens if the partnership ends — the same gap measured in an audit with no exit strategy; which performance metrics are contractual, and as of what date; and whether a commercial superlative, with its footnote, has made its way into one of your tender documents — the same question, for an ontology rather than a qubit, over who owns what a supplier builds on top of your data.
The two axes, applied to this case
Comply. Checking what a supplier has actually signed — and how far an organisation depends on a capability that lives in someone else’s cloud — becomes a control running on the client’s contracts and systems, with a critical-dependency register: for each critical capability, which legal entity owes it, under what instrument (contract, order, mere announcement), where it runs, which metrics are contractual and as of what date, and what happens at termination — with a dated record ready to show an inspector or a board.
Decide. The same system unifies contracts, suppliers, archives, systems and documents into a single operational model on which AI agents execute decisions with a human operator in command, for large enterprises, defence, the public sector and healthcare — the same question of stack ownership we raise on hardware and open-weight models. Always in two modes: on-premises on self-contained machines that require no deep integration into the client’s network, or a dedicated cloud with a dedicated VPN and a data centre in Italy, always with shared management.
From the first session, at no cost, comes the dated list of critical capabilities you buy from third parties: for each one, which legal entity owes it to you and under what document, which metrics are contractual and as of what date, and what is written about termination — including the boxes that stay blank. It stays with you even if we do not go on to work together. Talk to one of our engineers about it.