Not Fit for Purpose, Part II

Before the new platform family can be assessed, the chapter it was written to succeed must be properly closed.

A filing in the HII v. Cyberlux interpleader proceeding at EDVA documents the following: a dispute arose between HII, FEDSIM and CYBL over the utility of the drones in the battlefield theatre, and a Stop Work Order was issued December 22, 2023, just four months into the subcontract.

Four months. The subcontract was executed in August 2023. By December of the same year, a dispute over battlefield utility had produced a Stop Work Order. The word that matters in that filing is utility. Not compliance. Not delivery schedule. Not supply chain. Utility — in the battlefield theatre — which is the operational dimension of what Part I established technically.

This is not a regulatory finding or a paperwork failure. Part I said it on technical grounds. The court filing documents the operational dispute. Both arrive at the same place.

Any assessment of what Cyberlux offers next begins here, because the company asking for a second hearing is the same company whose first chapter ended with that sentence.

The new family has names built to carry weight — Spider, Huntsman, Tasmanian, Weaver. The specifications carry rather less. Each platform is assessed below against DDP Phase II requirements and the competitive market the program represents. The question is not whether each improves on the K8 in every respect. The question is whether any of them constitutes a credible path to DDP participation.

Four platforms. One specification entry, repeated across all of them, in the field that determines whether any of them can operate in the environment the DDP treats as its baseline: Comms — Customer Selection.

Customer Selection is not a specification. It is a blank field where a comms architecture should be. The November 2025 press release described platforms designed for high-performance operations in GPS- and RF-denied environments. The November 2025 spec cards, published the same week, delivered four blank comms fields. Those are not the same thing.

What the spec cards show is that the EW survivability problem documented in Part I has not been resolved at the platform level. It has been deferred — to the customer, to a future integration, to a date after the announcement. The DDP does not defer. It tests in an EW environment at the Qualifier, treats RF jamming resilience as a common mission objective across both areas, and scores RF-degraded performance as paramount at Gauntlet II. A blank comms field does not meet any of those requirements.

This is not a scored differentiator. It is listed as a common mission objective — the baseline operating assumption across both mission areas. The Qualifier pass/fail gates embed EW survivability as a prerequisite. A platform with no specified comms architecture does not have an EW survivability answer. It has a deferred question. The program does not defer questions.

The Gauntlet II evaluation criteria are more precise still. The RFS states that performance in degraded RF and GNSS environments is paramount. That word is not flavour text. Procurement language around weighted evaluation criteria is written carefully, and paramount means what it says — this is the dimension against which all other performance is measured. The programme is not asking whether a competing system has comms. It is asking whether the entire kill chain — target acquisition, control link, terminal engagement, detonation command — remains functional after the adversary attacks the thing most FPV drones depend on to operate. Customer Selection does not answer that question. It avoids it.

The Drone Dominance Program was designed by people who watched drone warfare in Ukraine and understood what surviving it required. The program's requirements — encrypted anti-jam comms as a baseline, GNSS-denied autonomous navigation, modular lethality integration through a standardised ESAD/EMSAD ecosystem, verified US supply chains, production at scale — are the lesson set the Ukrainian theater produced between 2022 and the present, formalised as a procurement framework.

The companies building credibly for this program have encrypted frequency-agile control architectures, autonomous navigation systems that operate without GPS, documented lethality integration, and production infrastructure capable of delivering thousands of units on fixed-price, penalty-carrying schedules. Their ceiling is above this program's floor.

The Cyberlux new lineup's ceiling — on the documentation available — is a twenty-minute FPV platform with no specified comms architecture, no documented GPS-denied navigation, and no ESAD/EMSAD integration. The Tasmanian may be capable in the right conditions with the right customer-selected comms solution. That is a different thing from being competitive.

This sentence calibrates the bottom of the evaluation distribution. The new lineup's documented capabilities place it in the category it describes.

The DDP Supply Chain Migration Schedule is not a compliance document in the ordinary sense. Its preamble states the purpose directly: the programme is using $1.1 billion in committed purchasing power as an advanced market commitment designed to create demand sufficient to justify domestic production scaling. This is not procurement. It is industrial policy executed through a purchase order. The government is not buying drones. It is attempting to build a sovereign industrial base — one that can sustain production at scale, under contested conditions, without dependence on adversary supply chains.

Ukraine provided the lesson. The schedule's preamble names it: supply chain resilience and industrial bases prepared to rapidly deliver at scale during conflict. The real weapon, as operators learned between 2022 and the present, is industrial continuity under contested logistics. The Migration Schedule is the mechanism by which the DoD is attempting to build that continuity domestically — creating the demand that justifies the investment that makes non-Chinese drone component supply chains economically viable at scale.

Every requirement in the schedule is a mechanism for that goal. The phase structure — Phase 2 Minimum, Phase 2 Preferred, Phase 3 Minimum, Phase 3 Preferred, Phase 4 Minimum — is a progressive ratchet. Each phase tightens the requirements until the Chinese component supply chain on which FPV platforms are built is no longer viable within the programme. What this means for a company entering Phase 2 with undocumented supply chains is not merely that they fail the current gate. It means they have no credible path to Phase 3 or Phase 4, because the requirements they cannot document today become more stringent at every subsequent phase.

The component table establishes thirteen supply chain categories, each with minimum and preferred requirements at every phase. Assessed against the Cyberlux new lineup, the picture is consistent across every category where documentation exists.

Component Area 7 — Motors — requires NCC assembly and ASDA-compliant entity at Phase 2 Minimum. The Weaver's BrotherHobby frame is manufactured in China. Motor sourcing is undocumented for the Huntsman, Tasmanian, and Spider. Component Area 8 — Propellers, Airframe and Structural Components — requires NCC assembly at Phase 2 Minimum. BrotherHobby is a Chinese manufacturer. The Weaver fails this category at the lowest compliance tier, documented in imagery the company published itself.

Component Area 2 — Communications and Data Link — requires NCC assembly and no Section 889 components at Phase 2 Minimum, advancing to NCC RF ICs and PCBs with firmware repos hosted and controlled by US entities at Phase 3 Preferred. Customer Selection means this category cannot be assessed for any platform. No comms architecture is specified. No component sourcing is documented. No firmware repository is identified. Phase 3 requirements — which the programme is already designing toward — assume a level of comms architecture documentation that Customer Selection structurally prevents.

Component Area 9 — Batteries and BMS — requires NCC pack assembly and prohibits procurement from CATL and entities listed under Section 1260H and FY24 NDAA Section 154 at Phase 2 Minimum. Phase 3 tightens to NCC cells compliant with Section 842 of the FY26 NDAA. Battery sourcing is undocumented across all four platforms. FPV platform heritage overwhelmingly suggests Chinese battery supply chain exposure. Component Area 11 — Ground Control System — requires NCC assembly and no Section 889 components at Phase 2 Minimum. No GCS is specified on any platform. Component Area 13 — Payload and Lethality — requires ESAD integration at Phase 2 Minimum, advancing to NCC ESAD/EMSAD meeting MIL-STD-1316 at Phase 2 Preferred, and US munition with US ESAD/EMSAD at Phase 3 Minimum. No platform documents ESAD integration.

The Migration Schedule also explicitly states that it is more restrictive than NDAA and is designed to progressively exceed statutory baselines. This matters because it closes the defence that retail investor narratives sometimes deploy: that NDAA compliance is the relevant standard. The programme itself says otherwise. The relevant standard is the Migration Schedule, and it is stricter, and it is published, and it is the gate that matters.

A company competing in the Drone Dominance Program is not competing on airframe capability alone. It is competing on trusted sourcing, auditable firmware, production resilience, scaling credibility, manufacturing survivability, and supply-chain sovereignty. These are not attributes that can be claimed in a press release. They can only be demonstrated through the documentation the programme requires, the production surveys it conducts, and the site visits it reserves the right to make. The new Cyberlux platform family documents none of them across the component categories the Migration Schedule identifies as critical.

The supply chain schedule is the mechanism of the trend. Across thirteen component categories, progressively tightening requirements systematically eliminate the Chinese supply chain from which FPV platforms are built — Chinese motors, Chinese ESCs, Chinese batteries, Chinese flight controllers, Chinese frames. Each phase tightens the requirements. Phase 2 Minimum establishes NCC assembly across every major component. Phase 3 adds NCC sub-components, NCC RF ICs, NCC encryption modules, firmware repos auditable by US entities. Phase 4 tightens further. What survives Phase 4 is not a manual FPV drone built on commercial components. It is an autonomous, EW-resilient, lethality-integrated platform with a fully documented, non-Chinese supply chain, firmware auditable on demand, and a production infrastructure capable of scaling under physical inspection.

The RFS signals this trajectory explicitly across both the evaluation criteria and the future phases description. Section 5.3.3 positions manual FPV at the bottom of the scoring distribution and names the differentiators the programme was designed to find — autonomous target engagement, force multiplication, autonomous behaviours in comms-denied environments, open architecture and interoperability. These are not features that can be added to a manual FPV platform. They represent a different design philosophy, a different supply chain, and a different production posture.

Section 5.4 — Future Phases — makes the trajectory explicit. Phase III introduces a semi-persistent test environment with GPS jamming and counter-UAS capabilities, warfighter-led evaluation in unscripted scenarios, mandatory integration with two or more munitions providers, and potential linkage through ATAK and Nett Warrior. Phase IV places a premium on rapid continuous improvement alongside high-volume production. The RFS states directly: companies that treat their product roadmap as fixed will find it difficult to remain competitive in Phase IV.

That sentence is not a general observation about competitive markets. It is a precise description of what happens to a company that announces a four-platform manual FPV family as its competitive answer to a programme built around a supply chain schedule designed to make that architecture obsolete. The programme is moving. The schedule is the mechanism. The evaluation criteria are the signal. And Cyberlux's response to a first generation stop-worked for battlefield utility failure was to double down on the supply chain the programme is designed to replace, at the capability tier the programme calibrates as its floor, with a comms architecture that cannot be specified and a manufacturing infrastructure whose recent documented history is a court officer counting individual screws.

The gap between that response and the programme's direction is not a gap in specifications. It is a gap in strategic comprehension of what the programme is actually for.

The DDP Phase II pricing structure is fixed in the RFS. Mission Area A: $4,500 per drone. Mission Area B: $3,500. These are the contract prices for every unit delivered, from the Stage 2 production test order through post-Gauntlet prototype delivery orders that begin at a minimum of 4,000 units.

A Signal message from Mark Schmidt places the all-in manufacturing cost of the K8 at $4,700 per unit. That figure was Schmidt's own representation, filed as ARG Exhibit B at EDVA ECF 167-1. No document in the public record establishes a lower manufacturing cost for the new platform family. No public filing or investor communication addresses the unit economics of DDP participation.

At Mission Area A pricing, every drone delivered generates a $200 manufacturing loss before overhead. At Mission Area B pricing, the per-unit loss before overhead is $1,200. At the minimum post-Gauntlet order of 4,000 units, the manufacturing loss before overhead for Mission Area A is $800,000. At 8,000 units — first place — it is $1.6 million. These figures exclude logistics, compliance costs, the SME training support the RFS mandates, and the 5% sparing requirement on every delivery order.

The per-unit economics have not changed. What has changed is the manufacturing infrastructure that would need to produce at those economics.

The receiver then attended the facility nearly daily. A court transcript from March 2, 2026 records his account: inventorying assets to the component level, counting individual screws — 4,492 of them — bagging and shipping them to the federal government as part of the final deliveries required under the subcontract termination.

The Spring, Texas facility is the manufacturing heritage of the entire Cyberlux platform family. It traces to Catalyst Machineworks — the Houston-based drone manufacturer Cyberlux acquired in March 2022, whose FPV lineage became the K8 and forms the engineering basis of the new lineup. Catalyst Machineworks is owed $1,860,017 in unpaid wages and compensation. The facility's landlord is owed $342,478. Employees have a collective claim of $2,676,378.

By June 2025, the receiver was seeking to abandon and return the facility to Cyberlux. Whether the facility was returned, and in what operational condition, is not established in the available public record. What the record does establish is that the manufacturing infrastructure from which any DDP production would need to come was under court-ordered receivership in May 2025, inventoried at the component level, with its workforce and its landlord both substantially unpaid.

The public record does not establish production infrastructure capable of supporting DDP delivery requirements. The per-unit economics are inverted at every price point the program offers. Neither condition is addressed in any Cyberlux public filing, press release, or investor communication available to this assessment.

One provision in the RFS connects the production analysis directly to the programme's evaluation architecture. Section 5.3.2 states that the production capabilities assessment may include production and manufacturing surveys, interviews, and site visits to production facilities conducted by Government inspection teams. This is not an auditing mechanism external to competitive scoring. It is a programme gate — one that determines whether a vendor's claimed production capability is real. The government will look. What the public record documents about Cyberlux's Spring, Texas manufacturing facility is not collateral to this analysis. It is the answer to the question the inspection team would ask.

This analysis has examined Cyberlux's claimed forward position across five dimensions: the court record that frames the transition from the K8 era, the new platform family's documented specifications, the comms architecture those specifications reveal, the competitive market those platforms would need to enter, and the production reality that would underpin any delivery.

The court filing documents an operational dispute over battlefield utility that produced a Stop Work Order four months into the subcontract. That is the starting line for any assessment of what Cyberlux offers next.

The new platform family does not constitute a credible response to it. The Weaver, presented as the family's trainer, carries Chinese manufacturer branding in its launch photograph — the same category of compliance gap the K8 carried in the same category of imagery. The Spider performs worse on endurance than the system at the centre of that operational dispute and exists only as engineering renders. The Huntsman cannot agree with itself on the payload specification that determines whether it clears the program's primary mission threshold. The Tasmanian is the most credible platform in the lineup and still ships with an empty comms slot, no documented GPS-denied navigation, and no ESAD/EMSAD integration in any available specification.

Customer Selection, repeated across all four platforms in the field that matters most, is a placeholder where a specification should be. The press release described platforms designed for GPS- and RF-denied environments. The spec cards delivered blank comms fields. What the record shows is an unresolved comms architecture across every platform the family contains — and a programme whose baseline operating assumption is the environment those blank fields cannot answer.

The public record does not establish production infrastructure capable of supporting the delivery requirements the DDP would impose. The per-unit economics are inverted before overhead at every price point the programme offers. The court transcript records a receiver counting 4,492 screws at a facility whose workforce and landlord were both unpaid. The programme will send inspection teams to physically verify what vendors claim about their manufacturing capability. The public record is the answer to what those teams would find.

The Drone Dominance Program requires supply chain compliance that the Weaver's documented component sourcing does not survive. It requires EW survivability that no platform in the family demonstrates. It requires ESAD/EMSAD integration that no specification documents. It would pay prices at which production is structurally loss-making before overhead. It requires a production record the public record does not establish. And across thirteen component categories, it requires a supply chain sovereignty that the new lineup cannot document.

The programme is not asking whether Cyberlux can build a quadcopter. That question was answered in 2023. The programme is asking whether a company is a viable node in a sovereign industrial system — one whose component sourcing can be traced, whose firmware can be audited, whose production can withstand physical inspection, and whose comms architecture can survive the electromagnetic environment the programme treats as given. These are the dimensions of industrial trustworthiness. Cyberlux fails them not in degree but in kind.

The narrative circulating in retail investor channels is not supported by the platform specifications, the production record, the court filings, the supply chain documentation, or the programme's own published requirements. Cyberlux is not failing a specification sheet. It is failing an industrial sovereignty test. The platforms are the symptom.

The record does not need much interpretation. Read in sequence, it does most of the damage itself.

Forty-eight requirements assessed across eight categories. Each platform evaluated independently against the DDP Phase II RFS. Filter by status to isolate failure type; filter by platform to focus on one system. Uniform rows — where all four platforms carry the same status — identify company-level architecture problems rather than platform-specific shortfalls.