Reading the Wolfpack Short Report on York Space Systems: A Single-Customer IPO Meets a Pentagon Procurement Pivot

On 11 May 2026, Wolfpack Research published YSS: Lost In Space — The Pentagon Just Killed 96% of York's Revenue, a short report against York Space Systems Inc. (NYSE: YSS) priced at $34.79 — a market capitalisation of $4.44 billion. Wolfpack's headline contention is straightforward: 96% of York's 2025 revenue came from selling Transport Layer satellites to the Pentagon's Space Development Agency (SDA), and as of late April 2026 the Pentagon has wiped out future funding for the SDA's Tranche 3 Transport Layer and announced its intent to dissolve the SDA itself, replacing the Transport Layer programme with a Space Data Network in which SpaceX's Starshield is the named backbone provider. York IPO'd on 28 January 2026, just under four months before that decision. We read the report against the public budget documents, contemporaneous reporting from Breaking Defense and Air & Space Forces Magazine, and York's own filings. This post lays out what Wolfpack alleges, the procurement evidence underpinning the customer-cancellation thesis, the operational and governance flags raised against York management, and where it sits inside a listed space sector that is, at the level of equity multiples, still very hot.

Short reports are not neutral documents. Wolfpack discloses that it holds, or expects to hold, a short position in York and stands to profit if the share price falls. That commercial interest is the right starting frame: the report is directional, but the underlying procurement decision — the part that does the heaviest lifting in the thesis — is not. The Pentagon's pivot away from the SDA's Transport Layer and toward a Starshield-anchored Space Data Network is documented in budget submissions and trade-press reporting that pre-date the short report. The customer-concentration arithmetic is in York's own 10-K. The operational and governance allegations are, by definition, contested — they rest on anonymised former-employee testimony and on Wolfpack's reading of the company's controls. We treat each layer on its own evidentiary footing.

Overview

1. York in one paragraph
2. The Pentagon's pivot from Transport Layer to Space Data Network
3. The customer-concentration arithmetic
4. Wolfpack's operational allegations
5. Internal controls, accounting, and governance flags
6. The macro: a hot sector, a consolidating procurement architecture
7. What is yet to be heard
8. Where we sit

York in one paragraph

York Space Systems was founded in 2012 by Dirk Wallinger, who is still the chief executive, and is headquartered in Greenwood Village, Colorado. The business builds satellite buses — the structural and subsystem platform onto which mission-specific payloads (sensors, communications gear, propulsion) are integrated — primarily for low-Earth-orbit missions. York has been one of the four contracted satellite vendors to the SDA's Proliferated Warfighter Space Architecture (PWSA) Transport Layer programme, the U.S. Space Force's planned low-Earth-orbit data-relay constellation, alongside Lockheed Martin, Northrop Grumman, and Rocket Lab. York priced its IPO on 28 January 2026 at $34 per share — the top of the marketed $30–$34 range — selling 18.5 million shares (upsized from 16 million) for total proceeds of approximately $629 million, and listed on the New York Stock Exchange under the ticker YSS. Q4 2025 results, reported in the first quarter of this year, put 96% of FY2025 revenue with the SDA and guided FY2026 revenue to a $545–$595 million range, with management telling analysts that roughly 70% of that figure is covered by existing backlog. The next earnings call is scheduled for 14 May. Wolfpack's report dates to 11 May, three days ahead of that print.

The Pentagon's pivot from Transport Layer to Space Data Network

The SDA, set up inside the Pentagon in 2019 and folded into the Space Force in 2022, was built around a single idea: rather than fielding a small number of large, expensive geostationary satellites, the U.S. would build a proliferated low-Earth-orbit mesh — hundreds of smaller, faster-to-replace satellites operating at lower orbits, networked together. The Transport Layer is the data-relay backbone of that mesh; the Tracking Layer is the missile-warning sensor side. Tranche 0 — the experimental tranche — has been in orbit since 2023. Tranches 1 and 2, totalling more than 300 satellites, were already under contract heading into 2026. Tranche 3 — approximately 140 satellites — was the next planned increment, expected to be ordered in 2026 for deployment from 2028.

In June 2025, the Pentagon's FY2026 budget request suspended Tranche 3 procurement. Congress reinstated $500 million in the subsequent appropriations cycle, but the policy direction had been signalled. On 22 April 2026, Breaking Defense reported that the Space Force was shifting away from the Transport Layer programme to a new Space Data Network (SDN) "backbone" for orbital relay. Six days later, the Pentagon released its FY2027 J-Books — the budget justification documents that, although dense, set out funding lines with line-item granularity. The J-Books name Starshield, SpaceX's national-security variant of the Starlink constellation, as the incumbent provider for the SDN backbone, and contain no competitive solicitation for a second backbone vendor. A Space Force official quoted by Air & Space Forces Magazine on 29 April said that identifying a second contractor remains planned, but provided no timeline, no solicitation, and no binding commitment. As of the date of Wolfpack's report, the procurement record points to a single-vendor backbone built on Starshield.

This is the centre of the short thesis. Wolfpack's reading is that the programme on which York based its IPO growth case — Tranche 3 wins on top of established Tranche 1 and Tranche 2 deliveries, and a continued role as the SDA's lowest-cost-per-satellite supplier — is being superseded by a procurement architecture in which York is not the named provider, and in which the second-source slot is at best speculative. The bull case requires one of three things: a binding Tranche 3 award that the J-Books contradict, a meaningful SDN second-source role that the current procurement record does not confirm, or commercial business that more than offsets the SDA shortfall — a category that, in York's filings, has historically been small.

The customer-concentration arithmetic

The mechanical part of the case is the simplest part of the report. Customer concentration is disclosed in York's FY2025 10-K, where the company reports that 96% of FY2025 revenue came from the SDA and that "substantially all" of its backlog is tied to that agency. Wolfpack reads management's FY2026 guidance — $545–$595 million, with a $570 million midpoint and approximately 30% of that midpoint flagged on the Q4 call as needing to come from new government contracts in the back half of the year — as implying around $170 million of in-year revenue that is materially exposed to a Tranche 3 outcome. The remaining 70% — about $400 million of backlog conversion — would be the floor under any contraction scenario, but is itself dependent on Tranche 1 and Tranche 2 deliveries running to schedule. Reporting in March 2026 placed the Tranche 1 satellites approximately three months behind, with a "strategic pause" on further launches through May or June. The backlog number is not necessarily wrong; the timing of its conversion is, on the evidence, less certain than the guidance implies.

The replacement-customer pipeline that Wolfpack assesses is, on the firm's reading, thin relative to what would be needed. York is one of a large pool of vendors on the Space Force's SHIELD vehicle for commercial satellite procurement — Wolfpack cites a vendor count of more than 2,400 — and one of twelve named to compete for STEP 2.0, a $237 million envelope spread across ten years. Distributed evenly, STEP 2.0 implies less than $2 million per vendor per year; if York won the entire envelope, it would still imply only around $20 million per year. The "commercial and other" revenue segment in York's own 10-K has not exceeded $14 million in any year since FY2023. None of this rules out a non-SDA growth path, but it does set a realistic ceiling on how quickly one could materialise.

Wolfpack's operational allegations

The non-mechanical part of the report draws on Wolfpack's conversations with current and former York employees. Wolfpack describes these sources as anonymised to limit retaliation exposure; the firm does not name them and acknowledges that the views are not always unanimous across interviewees. Three operational threads run through the testimony.

The first is the modular-versus-made-to-order allegation. York's S-1 and earnings-call language describe the company's competitive position as resting on a "modular satellite spacecraft architecture" — a standardised bus that can be configured for different missions, enabling faster build and lower unit cost than competitors. Multiple former employees told Wolfpack that this characterisation is, in practice, inaccurate. One described it as "false advertising about having a platform that's ready to go and just needs to be pulled off the shelf"; another framed York's modular system as an aspiration rather than a delivered capability ("they don't have that base yet"). A third stated that the satellites were "made to order" inside a programme that markets them as off-the-shelf. The accounting and procurement consequence, on Wolfpack's reading, is that the unit economics York advertises — the cost-per-satellite advantage that supposedly underwrote its Transport Layer wins — would, if accurate, depend on a maturity of platform that the testimony disputes.

The second is build quality and software readiness. Two former software engineers told Wolfpack that York's Tranche 1 satellites launched without their mission-critical software being independently verified, in order to keep the launch schedule. One described the in-flight outcome plainly: "they all have problems in flight." A separate former manufacturing employee told Wolfpack that, as Tranche 1 deadlines closed in, the company would "find the smallest level of test that would give them an indication it was okay" and proceed. The independently reportable corroboration is the March 2026 trade-press disclosure that Tranche 1 launches are running roughly three months behind, with a strategic pause through May or June. The post-launch performance reports are not yet in the public domain, but the SDA's published satisfaction with the broader Transport Layer programme — across all of its incumbent vendors, not York alone — has been deteriorating.

The third is customer information control. One former employee told Wolfpack that York's programme managers operated under instructions not to escalate engineering concerns to customers — paraphrased as "say anything and not check back with the engineers" — and that they did not consider it acceptable to remain part of a programme of this importance to national security under those constraints. Wolfpack uses this thread to argue that the Pentagon's dissatisfaction with the Transport Layer, which is itself documented across multiple incumbent vendors, was meaningfully driven by the gap between what York presented to the customer and what it delivered. The thread is the most contested layer of the three; it depends on the credibility of individual former-employee accounts that the firm does not name, and a fair reading is that it is one input into the procurement-shift question rather than the dispositive one.

Internal controls, accounting, and governance flags

The accounting concern is centred on segregation of duties. Multiple former employees told Wolfpack that, in a company of roughly 710 full-time employees, only one finance team member besides the chief financial officer had visibility into costs, cost approvals, and pricing. One former employee said that even ten-cent-washer purchases routed through that single approver — a description that, if accurate, implies a level of bottleneck that would be unusual in a company at York's scale. The same testimony suggested that internal cost transparency to operations was very limited.

York recognises revenue on a percentage-of-completion (POC) basis — booking revenue as costs are incurred against the total estimated cost at completion. POC is standard for long-duration, milestone-based contracts; it is also a method in which estimation error directly drives the reported topline. The risk-factor section of York's 10-K acknowledges this. Wolfpack's argument is that POC plus single-point cost visibility plus the modularity testimony adds up to a non-trivial risk of estimation drift, with revenue restatement as the worst-case outcome. The firm is careful to add that it has no direct evidence that a restatement has occurred or will occur. The flag is structural rather than specific.

The governance section of the report is more atmospheric. Former employees describe an "all-black office" layout chosen by the chief executive, a private floor with restricted-access elevator and restroom, and a policy that most employees enter the building through a back fire exit rather than the front door. Whether any of this would, in isolation, be material to a fundamental thesis is reasonably contested. Wolfpack frames it as colour rather than as load-bearing evidence; we read it the same way. The substantive governance question is the segregation-of-duties one above.

The macro: a hot sector, a consolidating procurement architecture

The framing within which all of this lands matters. By any reasonable measure, the listed space sector is in an unusually strong phase. Rocket Lab, Planet, AST SpaceMobile, BlackSky, and Intuitive Machines have each repriced higher over the past twelve months, and the broader basket of U.S. listed space-exposure names has materially outperformed defence-industrial-base peers. Public-market enthusiasm for proliferated low-Earth-orbit architectures — many smaller satellites in low orbits, providing communications, sensing, and missile warning — has rarely been higher. York's January IPO priced into that environment, and was multiple times oversubscribed.

The tension Wolfpack's report exposes is that the U.S. national-security procurement architecture, which is the largest single buyer of proliferated low-Earth-orbit services, is moving in the opposite direction. Starshield was first contracted by the Space Force in 2023 and has expanded steadily since. NASA awarded Starshield a sole-source contract for Deep Space Network support in December 2025. The April 2026 FY2027 J-Books name Starshield as the SDN backbone provider with no competitive solicitation for a second backbone slot in the current cycle. Whether one reads this as good policy or bad policy, the pattern is recognisable: the period in which the SDA distributed Transport Layer awards across multiple vendors is, on the present procurement record, ending. That has implications beyond York — Lockheed Martin and Northrop Grumman are also Transport Layer incumbents — but York is the listed vendor with the highest single-customer concentration on the programme. The macro tailwind around space exposure and the macro headwind around backbone procurement consolidation are not necessarily incompatible, but they point in different directions, and the resolution will run through specific contract awards rather than through sector sentiment.

What is yet to be heard

The proximate data points are knowable. York's Q1 2026 earnings call on 14 May will be the first opportunity for management to address the FY2027 J-Books on the record, to give a Tranche 1 launch-schedule update, and to walk through the back-half FY2026 guidance ramp in the context of a Tranche 3 environment that no longer exists in the form management appeared to assume on the Q4 call. The second is whether and when the Pentagon issues a competitive solicitation for a second SDN backbone vendor — a step that Air & Space Forces Magazine has flagged as planned but unscheduled. The third is whether the contracted Tranche 1 and Tranche 2 satellites accumulate further post-launch software or hardware issues that change the SDA's posture toward York's outstanding deliveries. The fourth — and the one the market will price first — is York's own response to the Wolfpack report. As of the date of this post, none of these points have been settled in public.

Where we sit

We build Plainview and Bollwerk Frontier to help research, risk, and compliance teams turn the kind of allegation that surfaces in a short report into a structured investigation of their own. The tooling sits over filings, contracts, procurement data, and management commentary the way an analyst does: customer-concentration disclosures in the 10-K, programme-line detail in the Pentagon's budget books, audit-committee and segregation-of-duties disclosures in proxy material, and historical performance against guidance across earnings calls. A short report is one input into a larger investigation, not a verdict. If your team is working through the York thesis — or any comparable single-customer, single-programme, government-procurement-exposed name — and would find it useful to compare notes, write to hello@bollwerk.ai.