Executive Summary
Central decision: The Navy will require different ship classes for different missions. Leadership must decide whether those classes will continue as disconnected acquisition efforts or be governed as one coordinated engineering family. TriSeadon proposes the latter: specialized hulls with common standards, interfaces, logistics, training, and modernization control.
TriSeadon requires an executive decision because the Navy's surface-force problem is no longer just a ship-design problem. It is a combined fleet, industrial, logistics, and modernization problem. Continuing to stretch aging destroyer logic and fragmented production capacity will keep delivery slow, competition narrow, and modernization late against a threat environment built around drones, missile raids, undersea competition, and long-range distributed warfighting.
This brief asks leadership to approve a controlled program answer. TriSeadon fields three purpose-built combatants inside one force architecture, locks common interfaces and refit discipline, establishes a Government Arsenal Standard for qualified multi-source production, and ties ship production to industrial expansion, module-campus participation, DLA-centered supply control, workforce growth, and yard cleanup. The point of the decision is to turn the concept into executable program authority, not to leave it as a long-form study without commitment.
The brief therefore focuses on the minimum leadership actions needed now: lock the current baseline, assign Navy-led authority, authorize phased industrial mobilization, preserve build-now discipline, direct independent validation of cost, schedule, and acquisition path, and use a 24-month startup block plus phased state rollout instead of pretending full national activation happens immediately. No ship is permitted to depend on an immature technology in order to be built or fight.
Table of Contents
- Decision Context and Leadership Problem
- Decision Required Now
- Decision Asks
- Baseline Lock and Scope Control
- Program Authority and Governance
- 24-Month Execution Block
- Industrial Mobilization and Yard Activation
- Technology Discipline and Block Insertion
- Cost and Schedule Controls
- Decision-Level Risk Register
- Decision Logic and Recommended Authorization
1. Decision Context and Leadership Problem
The leadership problem is straightforward: the current surface-force path does not produce enough combat depth, enough industrial depth, or enough modernization speed. The fleet problem and the industrial problem are now the same problem. A narrow yard base, proprietary chokepoints, and repeated redesign cycles are degrading the pace at which credible combat power can be fielded.
TriSeadon is presented as a program-level answer rather than a single-hull answer. Leadership is being asked to decide whether to continue managing fleet shortfalls through piecemeal extension of legacy paths or to authorize a force architecture designed around deliberate modernization and national production scale.
2. Decision Required Now
Decision is required now because the value of TriSeadon depends on early control, not late rescue. If baseline lock, governance, industrial sequencing, and technology insertion discipline are deferred, the program risks becoming another broad concept with no executable shape.
This brief therefore frames the immediate action as authorization of the program structure itself. The decision is not to buy every future subsystem today. The decision is to establish the fleet, industrial, and governance architecture that lets those later choices happen without reopening the entire program, while treating the first twenty-four months as a startup execution block and the fifty-state network as a phased rollout.
3. Decision Asks
The core asks are fivefold: lock the baseline, assign authority, authorize industrial mobilization, enforce build-now discipline, and direct independent validation. Those actions are the minimum viable executive package for turning TriSeadon into a controlled program.
Each ask is designed to close a known failure mode. Baseline lock stops drift, program authority stops governance ambiguity, industrial mobilization starts the capacity solution, build-now discipline blocks runaway immaturity, and independent validation gives leadership a hard review before larger commitments are made.
4. Baseline Lock and Scope Control
The decision cycle requires one authoritative baseline for class dimensions, mission roles, modular allocations, aviation baselines, and combat-system architecture. Without this lock, every downstream activity from ROM costing to yard planning becomes unstable.
Scope control is the companion rule. New ideas, alternative systems, and future inserts can continue in development lanes, but they do not modify the decision baseline unless they pass the formal block or refit gate. This is how the program avoids becoming self-defeating before first execution.
5. Program Authority and Governance
TriSeadon requires Navy-led governance because the program depends on a government-controlled baseline, government-controlled interfaces, and government-controlled production and support packages for new program-funded development. Contractors build, improve, and integrate against the program rules; they do not own the Navy's ability to reproduce, repair, or modernize its fleet.
The arsenal rule is one Navy baseline, multiple qualified producers, and interchangeable accepted output. Every new TriSeadon development RFP requires government ownership or equivalent perpetual controlling rights in the resulting foreground IP and complete production package. Controlled packages are released only to qualified and, where required, cleared U.S. sources. Existing privately funded background IP is not confiscated: exercise existing government rights where sufficient, purchase or license only when that is better value than replacement, or continue the legacy product while a government-owned successor is competed and certified.
The governance structure should therefore include configuration control, interface control, block-insertion review, industrial scoring, and independent validation gates. The objective is to preserve flexibility without surrendering control of the architecture to vendor-defined drift.
The authority decision must also protect continuity. Cancellation is outside the TriSeadon charter. Current carrier, submarine, amphibious, auxiliary, aviation, unmanned, sustainment, and decommissioning work continues, and DDG-51 construction continues during ramp-up. Suppliers may enter TriSeadon at startup or later; only accepted TriSeadon scope receives TriSeadon incentives and carries its new foreground-IP and technical-package obligations.
Open Government Arsenal Standard | Open Industry Transition | Open Shipyards Line | Open Technology Baseline
6. 24-Month Execution Block
The first 24 months are not a simple ship start. They are a multi-track execution block covering ship engineering, yard planning, DLA logistics expansion, technology RFPs, industrial siting, training pipelines, and environmental preparation. That block is what turns concept material into an executable acquisition posture.
The practical sequence is baseline publication, governance assignment, industrial readiness assessment, modular interface certification, early integration validation, and production-authorization packaging. The point is to emerge at the end of the block with decision-grade engineering and industrial readiness, not only narrative confidence.
All three class designs and their shared technologies are coordinated during development, but hull production follows the locked order of FFG first, CAG second, and DDG third. Major-yard and state-campus work proceeds concurrently through phased readiness gates rather than waiting for one national activity to finish before another begins.
7. Industrial Mobilization and Yard Activation
Industrial mobilization is not limited to major shipyards. It includes GOCO creation, GOGO modernization, COCO participation, module-campus activation, brownfield cleanup, workforce development, and DLA procurement expansion. The industrial decision is therefore as important as the fleet decision.
This section supports authorizing the industrial layer early because build schedules, cost realism, and modernization cadence all depend on whether the shipbuilding base is widened in time. Delay here would simply recreate the same bottlenecks the program is intended to solve.
The ramp is additive before it becomes transitional: existing workloads are protected, new and underused capacity is activated, and future surface-combatant starts shift only after TriSeadon passes readiness gates and receives separate authorization and funding.
Open Shipyards Line | Open Industry Transition | Open Yard Atlas
8. Technology Discipline and Block Insertion
TriSeadon's credibility depends on refusing to overload early flights with immature systems. Mature systems and stop-gap lanes are fielded first. New technology enters only through controlled block insertion after readiness, integration, and supportability gates are passed.
This section preserves the user-defined rule that no more than three major new technologies are introduced in a given flight or series version. That keeps the program aggressive without making it technically incoherent.
9. Cost and Schedule Controls
Cost and schedule control start with structural choices: frozen baseline, modular interface discipline, distributed production, stronger competition, DLA common buying, and predictable refit windows. The brief does not assume cost control appears later through accounting alone. It assumes cost control is designed into the architecture.
After a ship, module, or system production award, its capability baseline is frozen. Stakeholder enhancements move to the next hull, lot, flight, or scheduled 60-month refit. Only verified defect, safety, cybersecurity, physical or information security, legal or regulatory compliance, or unavailable-part form-fit-function corrections may alter current production, and those exceptions cannot add capability.
Continuity is earned but cannot be self-appropriating. If independent reviews confirm continuing fleet need and acceptable cost, schedule, quality, delivery, industrial, cleanup, workforce, and ROI performance, the Navy should retain TriSeadon as a program of record and request its minimum viable economic rate. Contractor points determine which qualified performers receive funded work; Congress retains authorization and appropriation authority. A proposed interruption should include a certified replacement plan and the full fleet, industrial, environmental, workforce, cancellation, restart, and lost-ROI consequences.
The engineering architecture remains useful even if the final Navy-approved hull differs from the current concept. Each mission requirement begins with a fielded system, advances through controlled integration and off-ship development, and reaches the fleet only after certification and DLA support are ready. The mature fallback stays available until the successor is accepted and stocked.
Leadership should therefore treat baseline discipline and industrial sequencing as financial controls, not just technical controls. Most major cost failures in naval programs begin as uncontrolled scope or industrial mismatch long before they show up in headline budget growth.
10. Decision-Level Risk Register
The decision-level risks are technical immaturity, industrial mismatch, supplier bottlenecks, requirements drift, and schedule inflation. None of those risks are ignored in this program. They are acknowledged explicitly and bounded through phased insertion, distributed capacity, DLA reserve control, and governance lock.
The key leadership point is that TriSeadon becomes more credible when it describes these risks openly and ties each one to a control mechanism. The brief is not asking for blind confidence. It is asking for approval of a structure designed to keep risk visible and manageable.
11. Decision Logic and Recommended Authorization
The recommended authorization is to approve the TriSeadon decision package as a controlled, phased national program rather than a notional fleet concept. That means authorizing the baseline, governance, industrial startup, validation block, and block-insertion policy together as one decision set.
The brief closes on a practical point: the Navy does not need another concept that remains outside program control. It needs a fleet-and-industry architecture that can be started now, disciplined over time, and modernized without recurring reinvention. This brief is the shortest path from concept to that decision.