How did DEPLOY correct the Red Cat Black Widow SRR contract value?

The framing error

Aggregator coverage of Red Cat Holdings (parent company of Teal Drones, maker of the Black Widow small unmanned aerial system) frequently surfaces the US Army Soldier Robotic Reconnaissance (SRR) program win at $55M contract value. The framing appears across press releases, defense industry coverage, and downstream secondary references.

The framing is wrong on multiple layers.

Per US Army FOIA primary-source verification, the actual Black Widow SRR contract is more nuanced:

• LRIP (Low Rate Initial Production) contract value: $12.9M, NOT $55M. The Low Rate Initial Production phase represents the initial obligated funding from the Army; the $12.9M figure resolves per FOIA-anchored primary-source verification.
• 5,880 systems is the Army OBJECTIVE quantity, NOT the OBLIGATED contract value. The Army's program objective represents the eventual desired procurement quantity; OBLIGATED funding is the committed contract spend at the LRIP phase. The two figures attach to different verification axes; aggregator coverage tends to conflate program-objective + obligated-funding into a single dollar-value claim.
• Black Widow replaced Skydio in the SRR program competition, NOT Black Hornet (FLIR's nano-UAV is a separate program with separate procurement structure + separate end-user mission profile). The aggregator framing conflating Black Widow with Black Hornet-replacement operates outside primary-source-anchored program-distinction.

Three distinct precision failures in aggregator coverage. Each operates at a structurally distinct verification layer.

---

The audit-first verification pattern

Per DEPLOY's standing operational discipline, defense-program contract claims operate at primary-source-verified depth. The audit-first verification pattern for program-contract claims:

• What is the program designation + procurement structure? Verify against named-program primary sources (Army contract awards database + FOIA responses + program-management office disclosures).
• What is the contract phase (LRIP vs full-rate vs prototype vs IDIQ)? Verify phase-specific funding obligations against contract-phase-specific primary sources.
• What is the obligated contract value vs the program objective quantity? Distinguish committed funding from program-target quantity at primary-source verification depth.
• What competition + predecessor relationships exist? Verify named competitors + replaced systems against program-management primary sources + competition-history disclosures.
• What aggregator-drift + source-quality patterns surface? Identify single-source claim patterns (short-seller reports + management framings + press releases) where the source carries verified primary-source-anchored figures + unverified allegation framings simultaneously.

Running the audit pattern on the Black Widow SRR contract surfaces the FOIA-anchored verification at $12.9M LRIP value vs the aggregator-framed $55M (program-objective conflation). The 5,880-systems figure resolves to the Army OBJECTIVE quantity rather than OBLIGATED funding. The program-competition history resolves to Skydio replacement (not Black Hornet).

---

The source-quality per-claim discipline

The Red Cat Black Widow correction surfaces a foundational framework-discipline pattern: source-quality per-claim, not per-source.

A single source can carry claims at structurally distinct verification depths simultaneously. The Kerrisdale Capital short-seller report (March 2025) on Red Cat operates as canonical worked example:

• FOIA-anchored figures verified at primary-source depth: the $12.9M LRIP obligated funding figure; the 5,880-systems Army objective quantity. These figures resolve at FOIA primary-source verification regardless of the reporting source's commercial position (short-seller).
• Allegation framings at lower verification posture: management-framing critiques; deployment-posture characterizations; commercial-trajectory assertions. These operate at single-source verification depth and require additional primary-source verification before they resolve at higher verification posture.

Per DEPLOY's how-deploy-verifies methodology editorial, the framework reads each claim at its own source-quality depth. The short-seller report carries verified FOIA figures + unverified allegation framings simultaneously; the framework doesn't reject the FOIA figures because of the source's commercial position, and doesn't accept the allegation framings because the FOIA figures verify at primary-source depth.

The source-quality per-claim discipline is structurally distinct from source-quality per-source. Per-source verification would either accept the entire short-seller report at single-source depth or reject the entire report because of the commercial position. Per-claim verification reads the FOIA-anchored figures + the allegation framings at structurally distinct verification depths.

---

The verified state: program-distinction + contract-phase + obligated-vs-objective

The corrected attribution per primary-source verification:

LRIP (Low Rate Initial Production) contract value: $12.9M obligated funding per Army FOIA primary-source verification. The LRIP phase represents the initial commitment + procurement structure for Black Widow systems within the SRR program; future phases (full-rate production or program continuation) would carry additional obligation cycles at the program-progression cadence.

5,880 systems Army OBJECTIVE quantity: program-target quantity per Army program documentation. The objective represents the eventual desired procurement scale; the obligation at the LRIP phase covers only the initial-rate-production fraction of that objective. Aggregator framings conflating the program-objective quantity with the LRIP obligated value into a single dollar-magnitude claim operate outside primary-source-anchored verification.

Black Widow replaced Skydio in SRR program competition: program-competition history per Army program-management disclosures. The SRR program competition selected Black Widow over Skydio at the procurement-decision phase. Aggregator framings asserting Black Widow replaced Black Hornet operate at program-distinction conflation; Black Hornet (FLIR's nano-UAV, much smaller class) operates within separate procurement structures and separate program-management context.

Black Widow vs Black Hornet class distinction: Black Widow is a small unmanned aerial system (sUAS) at a structurally larger class than FLIR's Black Hornet nano-UAV. The two systems target distinct mission profiles + procurement structures + program contexts. Aggregator framings collapsing the class-distinction into a single "Black Hornet successor" narrative operate outside primary-source-anchored verification of the class-distinction + program-distinction.

Per cap-flag-as-trust-signal, the verified state surfaces explicitly with the conflation rejections present at the per-claim layer. Each verified fact has its own primary-source anchor; each rejected framing operates outside primary-source verification at its own axis.

---

Why source-quality per-claim discipline matters

The Red Cat Black Widow correction operates as a worked example of source-quality per-claim discipline at the funding-source + program-source verification layer. The pattern recurs across the defense-procurement reporting space:

Single sources carry mixed verification depths. Short-seller reports, management framings, press releases, and trade-press pieces frequently contain primary-source-anchored figures (FOIA disclosures + contract values + program identifiers) alongside unverified allegation framings (management critiques + deployment-posture characterizations + commercial-trajectory assertions). The framework reads each claim at its own source-quality depth.

Per-claim verification catches conflations within sources. When a single source mixes verified figures + unverified framings, per-claim verification distinguishes the two. The FOIA-anchored $12.9M LRIP value verifies at primary-source depth regardless of the report's commercial position; the allegation framings operate at single-source depth and require additional verification.

Per-source verification produces wrong results in either direction. Per-source acceptance of a short-seller report at single-source verification depth treats unverified allegations as verified; per-source rejection of a short-seller report treats FOIA-anchored figures as unverified because of the source's commercial position. Both directions miss the verification depth that the per-claim framework produces.

Cap-flag transparency surfaces the per-claim distinction. Per how-deploy-verifies methodology editorial, the corrected attribution surfaces each verified fact at its primary-source anchor + each rejected framing at its source-quality verification depth. The discipline doesn't accept or reject sources wholesale; it reads claims at the depth where each claim resolves.

---

The drone cluster framework intersection

Per DEPLOY's autonomous drones cluster framework, the Red Cat Black Widow positioning operates within the new-defense AI-first cohort + manually-piloted-plus-assistive verification posture cluster. The Black Widow + Teal Drones + Red Cat Holdings entity stack anchors a specific drone-cohort position:

• Verification posture: manually-piloted-plus-assistive operations rather than fully autonomous mission execution. The framework reads Black Widow at the operator-supervised execution + assistive-AI tier within the autonomy-boundary classification cross-cohort taxonomy.
• Program-context positioning: Soldier Robotic Reconnaissance (SRR) program targets dismounted-soldier deployment scope at the squad-level reconnaissance mission profile. The program-context distinguishes SRR from larger-class drone procurement programs (Group 2 + Group 3 + Group 4 + Group 5 systems with structurally distinct mission profiles + procurement structures).
• Class-distinction: Black Widow at sUAS Group 1 class vs Black Hornet nano-UAV at distinctly smaller class with separate program context. The class-distinction matters editorially because procurement structures + mission profiles + program-management context operate at class-specific layers.

Per cluster framework, the program + class + verification posture distinctions all operate at primary-source-anchored verification depth; aggregator framings that collapse these distinctions miss the structurally distinct cohort-positioning that the framework reads.

---

Why this catch matters

The Red Cat Black Widow correction operates as a worked example of source-quality per-claim discipline at editorial-anchor depth. The catch demonstrates the framework discipline operating across multiple distinct layers simultaneously:

• Source-quality per-claim discipline: short-seller report carries FOIA-anchored figures + unverified allegation framings; per-claim verification reads each at its source-quality depth.
• Program-state precision discipline: LRIP obligated funding vs program objective quantity at primary-source verification depth.
• Program-distinction discipline: Black Widow replaced Skydio in SRR program, not Black Hornet (separate program with separate class + mission profile + procurement structure).
• Class-distinction discipline: Black Widow sUAS Group 1 vs Black Hornet nano-UAV at structurally distinct class layers.

Per how-deploy-verifies methodology editorial, the source-quality per-claim discipline operates as foundational framework discipline at the per-claim verification layer. Trade-press coverage of defense-procurement contracts compounds errors structurally: a program-conflation in one piece + a contract-phase conflation in another + a class-distinction conflation in a third produce the aggregator-framed "Red Cat won $55M Army contract to replace Black Hornet" framing that surfaces across downstream coverage. The framework discipline catches each layer at primary-source-verification depth; the corrected attribution surfaces honestly.

The catch demonstrates the discipline operationally at editorial-anchor depth. Per-claim source-quality verification produces the right number ($12.9M LRIP) + the right program identifier (Skydio replacement, not Black Hornet) + the right class-distinction (sUAS Group 1, not nano-UAV) + the right obligated-vs-objective framing (5,880 program objective, not contract value). Four distinct verification layers; one corrected attribution.

For the parallel framework-in-action correction-narratives, see How DEPLOY corrected the Figure 03 BMW narrative (three-layer aggregator-drift rejection) + How DEPLOY corrected the PI valuation (entity-distinction discipline) + How DEPLOY corrected the Covariant corporate-state (corporate-state precision) + Stryker isn't headquartered in Kalamazoo (small-fact discipline) + Monogram Doug Unis is CMO/founder, not CEO (small-fact role identification) + 1X Redwood is a captive brain, not humanoid hardware (entity-type discipline). For the methodology editorial canonical reference, see how DEPLOY verifies. For the autonomous drones cluster framework where Black Widow operates within the manually-piloted-plus-assistive verification-posture cohort, see the autonomous drones cluster. For the cross-cohort autonomy-boundary classification, see autonomy-boundary classification.