Mercury’s 8-K on Palantir has arrived: item 2.02, not item 1.01

On 18 August 2026 Mercury Systems, Inc. (NASDAQ: MRCY, CIK 0001049521) filed a Form 8-K with the SEC, accession 0001049521-26-000043. It is the follow-up to what we wrote on 6 August, when the agreement with Palantir Technologies, announced three days earlier in a joint press release, had no matching 8-K anywhere on EDGAR. The filing has now arrived. But in the weakest form the form itself allows: under Item 2.02 (Results of Operations and Financial Condition) and Item 9.01 (Financial Statements and Exhibits) — not under Item 1.01 (Entry into a Material Definitive Agreement). This is not the 8-K of the agreement. It is the quarterly 8-K, covering fourth-quarter and fiscal-year 2026 results for the year ended 3 July, in which the agreement surfaces only in passing, inside an exhibit.

Two exhibits, and a clause that defuses them before you even read on

There are two exhibits: 99.1, the earnings release (a2026q4earningsreleaseex.htm); and 99.2, the analyst presentation (q4fy26earningspresentati.htm). Under Item 2.02, the filing states, verbatim: “Information in Item 2.02 of this Current Report on Form 8-K and the exhibits 99.1 and 99.2 attached hereto shall not be deemed ‘filed’ for purposes of Section 18 of the Securities Exchange Act of 1934 … nor shall it be deemed incorporated by reference in any filing…” — the information under that Item and the two exhibits are not treated as filed for Section 18 purposes, nor incorporated by reference into any other filing. It is the same furnished versus filed distinction we measured on another announcement: there it was an Item 7.01, here an Item 2.02, but the shield from Section 18 is identical. An agreement attached to an Item 1.01 stays in the company’s permanent record, carrying the civil liability the law attaches to a filed disclosure; a furnished release under Item 2.02 does not.

One sentence, in one bullet, inside a slide

In the earnings release — Exhibit 99.1, the document anyone would read as the Mercury release — the word Palantir never appears: zero occurrences, checked against the text itself. The only mention of the agreement sits in the analyst presentation, Exhibit 99.2, as a bullet point among the quarter’s operating highlights: “Recently announced a strategic agreement with Palantir to leverage AI software to enhance material planning and factory operations in an effort to improve backlog conversion and deliver critical technologies to the warfighter.” A second mention, many slides later, is even more guarded: among the caveats to the fiscal-2027 and fiscal-2028 outlook, the same presentation states that guidance “does not incorporate any benefit from the Palantir partnership or other automation efforts.” Even in the one document that names it, Mercury is not willing to put the agreement inside a number.

Who knows how to use Item 1.01, and who is not using it here

Mercury is not a company that does not know how to disclose a material agreement. From 30 June 2015 to today, checked against data.sec.gov/submissions/CIK0001049521.json, 17 8-Ks have been filed carrying Item 1.01, the most recent on 4 November 2025 (items 1.01, 2.02, 2.03, 8.01, 9.01). On the other side, the four 8-Ks Palantir Technologies filed in 2026 — 2 February, 4 May, 3 August, all items 2.02/7.01/9.01, plus 9 June carrying only item 5.07 — do not contain a single Item 1.01. And in the 3 August 8-K, the very day of the joint press release (accession 0001321655-26-000039, itself 2.02/7.01/9.01), the word “Mercury” does not appear in any of the documents filed, quarterly release included: zero occurrences, in both files.

EDGAR’s full-text search confirms the same asymmetry at a wider scale. The index covers electronic filings from 2001 onwards — the whole of Palantir’s listed life, most of Mercury’s. Within that window, across every kind of filing Mercury Systems has made, the word “Palantir” appears exactly once: in the 18 August analyst presentation. Across every Palantir Technologies filing, the word “Mercury” never appears. A single document holds both names together — and it is the one the issuer states it does not want treated as filed.

The hierarchy that matters

This is not an irregularity. Materiality is the issuer’s call, and choosing Item 2.02 over Item 1.01 is not, in itself, a violation: it was legitimate for Quantinuum to choose Item 7.01, and it is legitimate here for Mercury to choose 2.02. But the form of a filing is itself information, and it reads in order: an agreement attached to an Item 1.01 sits in the permanent record, with consideration, term and exit terms open to anyone who wants to read them; an event disclosed under any Item still reflects a deliberate choice to disclose; a press release, even in full, remains the voice of whoever wrote it; a bullet point inside an analyst slide, in an exhibit the issuer itself carves out from Section 18, is the lowest rung — and it is exactly where the sole public reference to the Mercury-Palantir agreement sits today. The sentence, moreover, concerns backlog conversion: the same day, the earnings release claims a record backlog of more than $1.9 billion, up 38.4% year over year, and record bookings of $660 million, up 93.1%. That is the company’s performance, at the exact point investors look first, placed in the one corner of the filing that owes no accountability for its accuracy under the law.

See the service · Talk to an engineer

What to ask, when neither side files

Anyone evaluating a supplier that announces a “strategic” agreement without either party filing it as a reportable event still has questions to ask before writing it into an industrial plan or a board memo. Under which Item, if any, would the agreement be disclosed — and if the answer is a quarterly release, why not sooner. Whether the figure or the benefit claimed appears in a document the issuer itself exempts from statutory liability, or in the audited financial statements. Whether a claim about the supplier’s own performance — here, backlog conversion — is already measurable, or remains, as here, explicitly excluded from official guidance. None of these questions presumes wrongdoing: it only presumes knowing, before signing or trusting a claim, which rung of the document hierarchy it actually stands on.

The two axes, applied to this case

Comply. Checking which agreement a supplier has actually disclosed — under what Item, in what exhibit, under what liability clause — becomes a control running on suppliers’ public filings and on the client’s own contracts, with a critical-supplier register: for each one, the latest reportable event disclosed, the form of the filing, the date, and whether the liability carve-out covers the claim that matters to you — with a dated record ready to show an inspector or a board.

Decide. The same system unifies contracts, suppliers, financial statements and public filings 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. 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 suppliers whose latest material communication is not a filing but a bullet point: for each one, where the agreement is actually described, in what form, and whether the liability carve-out covers the claim you plan to use in one of your own documents. It stays with you even if we do not go on to work together. Talk to one of our engineers about it.