Executive Summary
National readiness finding: America did not simply lose ships. It lost fleet balance. In 2001, the United States Navy operated 27 cruisers, 53 destroyers, and 35 guided-missile frigates. As of August 12, 2026, seven Ticonderoga-class cruisers remain commissioned. USS Shiloh and USS Lake Erie are scheduled to inactivate on September 30, producing the five-cruiser FY2026 year-end projection. The FY2027 budget proposal would then retire USS Princeton, USS Robert Smalls, USS Gettysburg, and USS Chosin, leaving only USS Cape St. George. The Navy also projects 79 destroyers and no commissioned guided-missile frigates (FFGs) at FY2026 year-end. Destroyer capacity increased, but the dedicated frigate and cruiser layers largely disappeared, concentrating anti-submarine escort, air and missile defense, surface warfare, strike, and fleet-command requirements in one increasingly burdened force.
| Ship type | 2001 | FY2026 year-end projection | Change |
|---|---|---|---|
| Aircraft carriers | 12 | 11 | -1 |
| Cruisers | 27 | 5 (7 commissioned on Aug. 12) | -22 at year-end |
| Destroyers | 53 | 79 | +26 |
| Guided-missile frigates (FFG) | 35 | 0 | -35 |
| Submarines | 73 | 63 | -10 |
Threat finding: submarine forces and modern surface fleets are proliferating while the United States has no commissioned FFG. One published 2026 classification counts 419 frigates worldwide, including 46 in China and 0 in the United States. China is simultaneously continuing construction of cruisers, destroyers, frigates, and submarines. The need for persistent blue-water ASW escort, distributed sensing, off-board prosecution, and fleet-level undersea coordination is therefore increasing.
Industrial and environmental finding: the fleet cannot be separated from the system that produces it. Too few yards and suppliers carry too much work; facilities and equipment are aging; qualified labor is insufficient; and suitable former military and industrial properties remain contaminated or underused while surrounding communities carry environmental burdens and diminished employment.
Government-control finding: contractors remain essential partners, but the government must control the technical baseline, key interfaces, configuration data, sustainment rights, and competitive production pathways for its warships. Data-rights shortfalls, vendor lock, sole-source maintenance, limited spare-part access, and weak foreign-source visibility are readiness and lifecycle-cost risks, not merely contracting concerns. GAO documents the vendor-lock and sustainment consequences.
Central acquisition argument: The Navy will require different ship classes for different missions. The question is whether those ships will be developed as three isolated programs or as one coordinated engineering family.
TriSeadon response: rather than asking one increasingly complex destroyer family to absorb every major surface-combatant mission, TriSeadon restores three purpose-built classes: an FFG optimized for anti-submarine warfare, a DDG optimized for air and missile defense, and a CAG optimized for command, surface warfare, and naval fire support. The three ships are designed as one integrated fleet family with controlled standards, interfaces, systems where appropriate, logistics, training, and upgrade pathways.
Build-now, grow-through-life principle: detailed engineering and initial construction begin with mature systems, today's qualified workforce, and active U.S. shipyards while added industrial capacity is developed in parallel. Each class protects quantified margins for space, weight, stability, electrical power, cooling, data, access, and modular interfaces. Certified technology can therefore enter later flights and scheduled refits without reopening the hull or interrupting the production line.
The Congressional Budget Office's August 2026 analysis provides an independent measure of that challenge. CBO estimates approximately $275 billion for 15 nuclear-powered guided-missile battleships through 2056 and projects that the Navy's plan would increase large-surface-combatant construction tonnage by about 60 percent. TriSeadon accepts that report as a cost and industrial-capacity benchmark. It does not claim CBO endorsement; it proposes a conventional CAG-3 proof hull and a distributed three-class production architecture that must demonstrate lower recurring cost, faster learning, and broader capacity through measured results.
TriSeadon answers that problem as one connected national program. Tri-Class restores mission specialization; Tri-Power (gas turbines, diesel-electric, battery) provides operating flexibility and resilience; Tri-Modular (ISO, IMM, IWM) creates controlled upgrade paths; Tri-Unmanned (UAV, USV, UUV) makes off-board systems part of the fleet architecture; and Tri-Weapon (guns, missiles, directed energy) preserves layered combat options. Dedicated aviation, Drone Monitoring and Control, common JP-5 logistics, shared interfaces, and a scheduled five-year refit cycle keep the force current without reopening the entire ship design whenever a subsystem changes.
The white-paper argument is not limited to the ships themselves. TriSeadon also rebuilds the industrial system that makes the ships possible. It expands through government-owned contractor-operated yards, modernized government yards, competitive private-yard participation, a 50-state module-campus network, DLA-centered procurement and reserve control, workforce pipelines, and brownfield cleanup tied directly to yard and campus activation. The program is therefore a fleet-modernization effort, an industrial-revival effort, an environmental-reclamation effort, and a jobs-and-training effort under one architecture.
The implementation model is phased and consistent across the program: a 24-month startup block to lock design, governance, cleanup, logistics, yard activation, and training, followed by wave-based national rollout rather than immediate simultaneous activation in all fifty states. The funding model is likewise replacement-oriented, opening money from the legacy surface-combatant path and combining it with industrial, cleanup, and state-match mechanisms instead of assuming a purely additive budget.
Table of Contents
- Executive Overview and Strategic Decision
- Strategic Context and Threat Environment
- Current Fleet and Industrial Model Gaps
- TriSeadon Fleet Architecture
- Warfighting Concept and Operational Employment
- Ship Class Technical Framework
- Modular Combat Architecture
- Weapons, Sensors, and Mission Systems Roadmap
- Industrial Base Architecture and Yard Network
- Workforce, Training, and National Participation
- Logistics, Supply Chain, and DLA as Broker
- Cost, Affordability, and Program Economics
- Comparative Cost Analysis: TriSeadon vs. Legacy Surface Combatants
- Governance, Contracting, and Oversight
- Risk Register and Mitigation Strategy
- Strategic Outcomes and Measures of Effectiveness
- Recommendations and Authorization Package
- Decision-Support Documents
1. Executive Overview and Strategic Decision
This section states the central decision plainly: the Navy can continue concentrating expanding requirements in a limited number of increasingly complex ship programs, or it can restore mission specialization within a controlled common architecture. TriSeadon is structured to be buildable with mature systems, expandable through certified interfaces and protected service-life margins, and maintainable through planned refits instead of crisis redesign. Future capability is enabled by the architecture, but fleet construction does not wait for unproven technology. The design directly addresses the DDG-51 Flight III lesson documented by GAO: major system insertion into a mature hull can consume limited weight, stability, internal-volume, power, and cooling margins and constrain later modernization. Open the GAO assessment.
The executive decision package centers on locking the baseline, assigning program authority, authorizing industrial mobilization, preserving build-now discipline, and accepting that implementation begins with a 24-month startup block before wider fleet-scale production and national yard activation. The emphasis is on turning the concept into a controlled program rather than letting it remain an idea without executable governance.
2. Strategic Context and Threat Environment
The strategic case begins with the operating environment: drone swarms, dense missile raids, contested littorals, undersea competition, and longer-range distributed maritime warfare. A fleet built around too few ship classes, weak industrial replacement depth, and slow modernization cycles is poorly matched to that environment.
TriSeadon argues that the threat environment requires more than incremental upgrades. It requires a fleet that can combine sensors, shooters, modular mission packages, and refit cycles with a stronger shipbuilding base behind it. The strategic context therefore drives both the ship design and the industrial design at the same time.
3. Current Fleet and Industrial Model Gaps
This section defines the failure points in the current path: legacy hull extension, weak competition, proprietary bottlenecks, limited yard capacity, and modernization too dependent on one-off redesign. It also highlights the broader national problem of abandoned shipyards, dead industrial ground, and labor pools that no longer connect to naval production.
TriSeadon frames these not as isolated defects but as one system failure. The fleet underperforms partly because the industrial model underperforms. Any solution that ignores the shipyard base, supplier depth, and training base would repeat the same cycle at a larger cost.
4. TriSeadon Fleet Architecture
The fleet architecture is built around three roles inside one combat system family: FFG for ASW and sea-lane control, DDG for AAW and missile defense, and CAG for command, heavy surface war, and shore support. The ships are not intended as isolated programs. They are intended as interoperable combatants with shared interfaces, modular insertion paths, and fleet-level force multiplication.
This section also explains why the architecture is designed as a family instead of a set of unrelated point solutions. Shared interfaces and common standards reduce lifecycle churn, simplify training, and make the five-year refit model practical.
5. Warfighting Concept and Operational Employment
The operational concept centers on layered warfare rather than single-system dependency. Guns, missiles, energy weapons, unmanned systems, chaff, decoys, and EW are designed to operate together. The FFG develops and holds undersea and littoral contacts, the DDG leads the air-defense and strike screen, and the CAG carries the heaviest command, aviation-assault, and surface-war burden.
This section also covers force-multiplier logic: the best-positioned shooter should fire, the best-positioned sensor should track, and the fleet should share the picture instead of forcing every ship to solve every problem alone.
6. Ship Class Technical Framework
The technical framework locks the class differences and the class commonalities. FFG is ASW-first and acoustically disciplined, DDG is speed and air-defense focused, and CAG is stability, command, and heavy-strike focused. Shared standards exist wherever they help maintenance, training, modularity, and sustainment, but the hulls are no longer forced into one common underwater shape.
The section also captures the major dimensions, propulsion logic, mission spaces, and embarked-force posture for each class. The purpose is to move the ships from concept labels to technically anchored roles.
7. Modular Combat Architecture
The modular architecture is built around LCB, IWM, IMM, ISO, Cerberus, and SCUTUM interface rules. IWM carries major weapons, Cerberus carries integrated terminal-defense systems, and SCUTUM carries distributed light-defense and force-protection payloads. The point is not modularity for its own sake. The point is to make future systems fit a known fleet-standard interface family so new capabilities can be installed on new ships or inserted during refit without reopening base hull design.
The Government Arsenal Standard extends that logic inside the interface. New TriSeadon development RFPs require government ownership or equivalent perpetual controlling rights in foreground IP and complete build-to-print and support packages so qualified U.S. manufacturers can produce interchangeable accepted components and systems. Security controls determine who may receive sensitive data; they do not give one supplier a permanent veto over production or repair.
Legacy privately funded IP is not confiscated. The government first determines whether existing contracts already provide sufficient rights. If they do, those rights may be exercised case by case. If they do not, the government buys or licenses only when that is better lifecycle value than a replacement RFP; otherwise, it continues using the legacy system until a new government-controlled successor is tested, accepted, stocked, and ready.
This section explains why heavy mission and weapon changes belong in drydock-installed modules, while port-side mission flexibility belongs in ISO-sized swaps. It also reinforces the no-redesign rule that holds the whole program together.
Open LCB Architecture | Open ISO Mission Modules | Open Chapter 7
8. Weapons, Sensors, and Mission Systems Roadmap
This section tracks what is fielded now, what is transitional, and what is planned for later block insertion. It includes SPY-6 family radar, SQQ-90 family ASW baselines, Mk 57 PVLS, APM strike lanes, Trinion, Cerberus, DMC, AEGIR, PRIME, and Odyssey, while preserving stop-gap paths when end-state systems are not yet ready.
The core argument is discipline: mature systems are used first, future systems are inserted only after readiness gates are passed, and no more than three major new technologies are added in a single flight or block.
9. Industrial Base Architecture and Yard Network
The industrial architecture expands through GOGO, GOCO, COCO, and a 50-state module-campus network. Full shipyards handle erection, launch, integration, commissioning, overhaul, and deep refit. Module campuses build large sections, integrated assemblies, mission packages, and long-lead components in distributed form. The national network is phased by rollout waves rather than activated everywhere at once.
The expansion begins in parallel with the active Navy portfolio. Current carrier, submarine, amphibious, auxiliary, aviation, unmanned, weapons, sustainment, overhaul, conversion, inactivation, and decommissioning missions continue, and DDG-51 remains the destroyer-production bridge while TriSeadon matures. Existing docks, suppliers, and workers are not counted as available TriSeadon capacity without a funded transition plan.
GOCO site planning and acquisition, GOGO cleanup and modernization, COCO investment, state-campus rollout, ship engineering, and supplier qualification proceed on concurrent but phased tracks. Hull production is not simultaneous: FFG enters first, CAG second, and DDG third, with shared technology and module learning carried forward across the family.
This section also makes clear that yard activation is not only a production decision. It is also a cleanup and waterfront-recovery decision. Brownfield reclamation, underused industrial ground, and wider labor-pool activation are part of the industrial strategy itself.
Open Shipyards Line | Open Industry Transition | Open Chapter 9
10. Workforce, Training, and National Participation
TriSeadon treats workforce as a national capacity issue, not just a local hiring issue. Portable credentials, cross-yard training, union and community-college pathways, VA pipelines, and contractor scoring tied to workforce performance create a broader labor base that can support both build and refit demand.
The workforce section is also where the 50-state participation logic becomes politically and economically real. A distributed module network means more places can train, build, and enter the industrial system than under the legacy yard model.
11. Logistics, Supply Chain, and DLA as Broker
Logistics is organized around DLA as the active procurement, acceptance, reserve, and delivery broker, with a qualified civilian counterpart lane preserving competition. DLA buys common items, governs module acceptance, sets delivery timing, and maintains reserve depth so shipyards do not stop because one vendor slips or one shipment misses.
DLA and NAVSEA also administer the controlled production library: current technical packages, approved sources, configuration records, material pedigrees, government acceptance criteria, tooling status, obsolescence notices, and alternate-source readiness. A part is common only when its fit, function, quality, and configuration are verifiably interchangeable.
This section also defines the distributed sustainment loop: replacement inventory is installed first, removed items go back into a rebuild and recertification flow, and module campuses plus regional yards support sustained operations rather than one-time hull delivery.
12. Cost, Affordability, and Program Economics
The cost case is built around disciplined design control, distributed module pre-outfitting, stronger yard competition, DLA buying power, and reduced redesign churn. The claim is not that larger ships are inherently cheap. The claim is that a more coherent fleet and industrial system can reduce the waste that currently drives cost and delay.
CBO's August 2026 battleship estimate is the independent upper benchmark for the CAG affordability case: approximately $23.4 billion for the lead nuclear ship, $18.0 billion on average for later nuclear ships, $21.3 billion for a lead conventional alternative, and $15.9 billion on average for later conventional ships, all in 2026 dollars. TriSeadon targets a 20-30 percent recurring construction-cost reduction through conventional propulsion, competition, common systems, modular construction, learning-curve effects, and fleet-wide logistics. A mature 40-50 percent difference relative to CBO's constrained nuclear case is an upper-bound objective requiring demonstrated production performance and independent validation, not a budget assumption.
The section separates direct hull economics from industrial-capital economics. GOCO, COCO, and state module campuses each have different recovery models, while GOGO investment is justified primarily through readiness and sovereign capacity return rather than lease revenue.
Open Financials Line | Open CBO Alignment | Open Complete CBO Report | Open Chapter 12
13. Comparative Cost Analysis: TriSeadon vs. Legacy Surface Combatants
This section compares TriSeadon classes against historical analogs and current U.S. programs. It frames the FFG against current frigate logic, the DDG against Flight III Burke and DDG(X), and the CAG against the cruiser role, the Zumwalt warning case, and CBO's August 2026 nuclear and conventional battleship estimates.
The CBO comparison makes the industrial argument measurable. TriSeadon must show whether a GT/DE/PRIME CAG, government-controlled interfaces, additional qualified yards, distributed module production, and common work across FFG, DDG, and CAG can reduce labor hours, rework, schedule delay, lifecycle support cost, and proprietary integration expense. CAG-3 is therefore the proof hull used to establish actual cost and performance before the production claim is accepted.
The comparison must consider delivered combat capability, production time, lifecycle cost, modernization expense, and operational availability per appropriated dollar rather than displacement cost alone.
14. Governance, Contracting, and Oversight
Governance holds the program together through baseline lock, configuration control, interface control, accepted technical packages, stage gates, and scored contractor performance. The contracting logic is designed to widen competition without surrendering government control over the architecture or the practical ability to reproduce and sustain it.
This section also reinforces the rule that new systems do not reopen awarded production. The Navy keeps the technical baseline and secure production library, contractors build and improve against it, and funding is released through readiness and execution gates rather than drift. Once a ship, module, or system is awarded, capability changes move to the next hull, lot, flight, or scheduled 60-month refit. Current-production exceptions are limited to verified defect, safety, cybersecurity, physical or information security, legal or regulatory compliance, or unavailable-part form-fit-function corrections that do not add capability.
Program continuity is performance-conditioned rather than automatic. Verified delivery, quality, affordability, fleet need, industrial growth, environmental recovery, workforce results, and ROI support a minimum viable Navy budget request and legally available multiyear procurement tools. Contractor points allocate work within appropriated funds; they do not bind Congress. Any proposal to interrupt a performing program should present a certified replacement path and the complete fleet, industrial, environmental, workforce, cancellation, restart, and foregone-ROI effects.
The technology ladder is independent of any single concept hull: every mission has a fielded baseline, controlled integration step, developmental objective, certification gate, and later-hull or refit insertion path. The final FFG, CAG, DDG, or separately authorized derivative must still complete class-specific engineering, but no immature system is allowed to hold ship construction hostage.
Industry entry is voluntary and remains open after startup. Existing contracts retain their actual terms; firms accepting new TriSeadon development accept its foreground-IP, production-package, interface, quality, security, and qualification obligations for that scope. Cancellation remains outside the TriSeadon charter. Future surface-combatant demand shifts only after replacement capability exists and through separate Navy and Congressional decisions.
The government must also fund the people and facilities needed to administer this model: NAVSEA design and configuration authority, contracting and cost staff, IP and patent counsel, software and data specialists, DLA procurement and supplier-development teams, inspectors, test facilities, secure repositories, qualification tooling, and second-source certification. Rights on paper are not useful unless the government can validate and exercise them.
Open Government Arsenal Standard | Open Industry Transition | Open Decision Brief | Open Chapter 14
15. Risk Register and Mitigation Strategy
Risk is divided across technical integration risk, industrial-base risk, logistics risk, cost and governance risk, and schedule risk. The mitigation strategy is consistent throughout the program: stop-gap paths stay active, new tech is phased by block, distributed capacity reduces choke points, and the five-year refit cadence provides predictable modernization windows.
The risk section argues that TriSeadon becomes more credible, not less, when it openly admits where the program can fail and then shows how those failures are bounded by design discipline and industrial structure.
16. Strategic Outcomes and Measures of Effectiveness
The strategic outcomes are broader than fleet numbers. The program is measured by fleet relevance, industrial throughput, modernization pace, reserve depth, yard competition, labor growth, cleanup progress, and long-term ability to sustain sea power without the same recurring bottlenecks.
Measures of effectiveness therefore include operational capability, yard activation, module-campus maturity, workforce expansion, and whether the Navy can keep ships current on schedule rather than letting the fleet age out of usefulness between major recapitalization waves.
17. Recommendations and Authorization Package
The final section consolidates the program asks: lock the baseline, assign authority, authorize industrial mobilization, preserve stop-gap pathways, fund the 24-month startup execution block, and structure national activation as phased rollout rather than full simultaneous expansion. It also ties the fleet, shipyards, logistics, workforce, cleanup, and financial controls into one authorization logic rather than a loose collection of separate requests.
This is where the white paper turns from argument into action. The program is presented as a fleet that can be started now, modernized on schedule, and sustained over decades if the decision package remains disciplined, the early execution block is protected, and the industrial rollout remains phased and controllable.
Decision-Support Documents
These controlled companion pages separate evidence, proposal baselines, maturity, risk, terminology, and plain-language questions from the white-paper narrative.