Ship design leads into a broader procurement problem: many practical expectations were once left unwritten because designers, civil servants, and manufacturers shared institutional knowledge. The cited figures are roughly 1,500 requirements for Ajax against about 200 for the earlier CVR(T) family, with an explicit warning that the numbers had not been independently researched. Some of the growth may reflect roughly forty years of technical change and the erosion of legacy organizations able to translate military needs without spelling out every detail. Modern international contracting creates another incentive to specify everything because an unstated expectation can be omitted or traded away. The comparison is a qualified argument about procurement culture and does not establish that requirement count alone explains Ajax's difficulties.
Notable Point · 1:05:43-1:08:37
How requirements growth reflects institutional change
A qualified Ajax and CVR(T) comparison links longer specifications to technical change, contracting incentives, and reduced reliance on shared institutional assumptions.