By Al Vigier, 27 August 2026
Jeff Gilmour's 7 August post asked whether Canada can afford 15 River-class destroyers and 12 submarines, and the responses from David Dunlop and Ted Barnes argued fleet mix, rotation cycles and timelines. It is a good debate. It is also being conducted entirely in the currency of hulls and dollars, and I want to suggest the thread is missing the variable that will actually determine whether these ships are worth what we pay for them in 2045.
Software.
Consider what a River-class destroyer is, functionally. HMCS Fraser, whose keel was laid on 12 June, will carry an Aegis-based combat system paired with the SPY-7 radar, integrated by Lockheed Martin Canada, on a hull derived from BAE Systems’ Type 26 design. That is three design authorities on one warship, none of them Canadian, on a platform intended to serve into the 2050s and beyond. The steel will be cut in Halifax. The question nobody in this thread has asked is who holds the pen on the code.
The Halifax-class experience is the cautionary tale, and this readership knows it better than I do. The frigates received one great mid-life combat system modernization, a $4-billion investment, because the combat system was treated the way the hull was treated: fitted once, upgraded in a block, decades apart. That model is dead. A modern combat system is not a fitted system. It is a continuously updated one, with threat libraries, sensor fusion logic and fire control software revised on cycles measured in months. The US Navy manages Aegis as a living baseline for exactly this reason. A ship whose software is current is a different weapon from the same ship two baselines behind.
Which raises questions that are contractual, not technical, and that get settled now, while the ink is still wet, or never.
Who holds update authority over the River-class mission software? When a new threat emerges, does the Royal Canadian Navy receive the revised baseline on Canada’s schedule or on a release schedule set in Washington and Moorestown? Can Canada modify the combat system of its own warship, integrate a Canadian sensor or a Canadian weapon, without entering a foreign approval loop? What technical data rights did Canada secure: source access, interface documentation, the ability to test and certify changes in a Canadian facility? And is any of this scored in the industrial benefits attached to the program, or did the obligations count the steel and leave the software to the annexes?
I do not know the answers. That is partly the point. The public record on this program is rich in displacement figures, cell counts and delivery dates, and nearly silent on software governance. When the design refinements were presented in March, the coverage counted the vertical launch cells. Nobody asked who certifies the software that fires them.
The submarine decision multiplies the question. The selection of TKMS in July adds a fourth foreign design authority to the future fleet, with contracting to be completed by the end of 2027. Every clause about combat system data rights, update authority and Canadian integration capacity is being written in the next 18 months. After signature, those rights are bought back at monopoly prices or not at all.
Three things would answer the concern, and all three are cheaper than a single ship.
First, negotiate software data rights and update authority as capability, with the same seriousness applied to radar performance, and say publicly that it has been done. Allies extract these rights when they insist. Canada is a Type 26 partner alongside the United Kingdom and Australia, both of which have fought and partly won this fight on their own programs.
Second, build the sovereign shore capability to use those rights: a Canadian land-based integration and certification facility where combat system changes can be developed, tested and accredited. Rights without the means to exercise them are decoration.
Third, count software sustainment in the industrial obligations. Canada’s revised industrial benefit rules now reward intellectual property transfer. Applying that to combat system sustainment, deliberately and visibly, would put Canadian engineers inside the update cycle for 30 years, which is worth more to the Navy and to industry than another machined assembly.
Gilmour asked whether we can afford the fleet. Fair question. But the $84-billion argument is an argument about acquiring hulls, and a hull is the part of a warship that ages slowest. Whether these ships are still relevant weapons in 2045 will be decided by whether Canada can keep their software current, and on whose authority. That is the bill nobody in this debate has priced, and unlike the hulls, the price is being set right now.
Al Vigier is the founder and CEO of Caseway, a Vancouver-based AI company. He served seven years in the Canadian Army.
