The Five Architectural Principles That Travel
The Ukrainian-specific elements of the stack — the Ukrainian state, the Ukrainian military, the war, the particular history of the post-Maidan volunteer movement, Ukraine's specific relationship with Estonia and other digital-infrastructure donors — do not transfer. The principles beneath them do. Five principles are sufficient to characterise the architecture, and each has an analogue that could be instantiated in British institutional form.
3.1 Federation, not centralisation
Trembita does not centralise data. Each state registry — birth records, vehicle registration, tax, property, medical, military — keeps its own database, under its own ministry, and exchanges information with other registries through a cryptographically authenticated common protocol. DELTA does not centralise battle management; it is a platform to which modules connect through common identity and data layers. DOT-Chain Defence does not centralise procurement; it is a marketplace through which buyers and sellers transact while Prozorro provides the audit trail. The architectural pattern is federated: common standards, distributed ownership, interoperability through API.
The default British institutional instinct is toward centralisation — single systems, single owners, single accountability lines. This instinct is understandable in parliamentary terms (unified accountability is easier to scrutinise) and in Treasury terms (unified budgets are easier to control), but it produces the specific failure mode of monolithic IT programmes that cannot be incrementally improved and must be replaced wholesale at great expense when they become obsolete. The NHS National Programme for IT is the canonical British example; there are defence analogues. A federated architecture, by contrast, permits individual components to be updated, replaced, or added without affecting the rest, and permits multiple suppliers to compete at the component level while preserving system integrity.
3.2 End-user selection authority
DOT-Chain Defence permits brigade-level units to select which drones to procure, against state-funded points earned through combat effectiveness. The procurement officer does not choose; the commander closest to the tactical problem chooses. This inverts the Western model in which a central procurement authority selects equipment on behalf of units that will use it and deliver it through the supply chain.
The principle applies beyond drones. It applies wherever the operational requirement varies by context, by terrain, by adversary tactics, or by individual unit preference — which is to say, wherever the equipment is not a strategic platform procured in fleet numbers. For the British Army in particular, the principle would produce a material shift in how small-unit equipment (night vision, individual weapons ancillaries, communications accessories, drones of all classes, counter-drone systems, electronic warfare) is specified and procured. The brigade commander knows better than the Defence Equipment and Support desk officer what kit works on their particular operational problem. The current system treats this knowledge asymmetry as an administrative inconvenience; the Ukrainian system treats it as the core design constraint.
3.3 Marketplace, not catalogue
The procurement architecture is a marketplace in the economic sense: multiple certified suppliers list products with live availability, end users select from the available range, and the state's role is to operate the certification process and the payment rails rather than to pre-select or pre-contract specific products. New suppliers can onboard through a defined process. Products can be added, updated, and removed as they are developed or rendered obsolete. Demand signal flows from buyers to sellers with minimal intermediation.
The British procurement analogue is the Crown Commercial Service framework, which is catalogue-structured — pre-selected suppliers, pre-negotiated rates, pre-defined product categories. Frameworks of this kind are adequate for stable commodity categories (stationery, basic IT equipment) but are structurally incapable of keeping pace with categories where products evolve faster than framework cycles. Defence technology is now such a category in several product classes. A marketplace architecture would require legislative carve-outs (the Procurement Act 2023 permits dynamic purchasing systems, but the detailed operating model would need to be constructed) and institutional capacity (a certification authority equivalent to Brave1's), but the underlying legal framework exists.
3.4 Feedback loops integrated into procurement
The Army of Drones Bonus programme is the most conceptually original of the Ukrainian innovations. It welds together the kill chain and the procurement chain into a single integrated system. Combat effectiveness — measured by verified target destruction uploaded to DELTA — generates points. Points are spent on equipment through Brave1 Market. Equipment is fulfilled by the Defence Procurement Agency through DOT-Chain Defence. The effect is that units that actually destroy enemy targets receive more resources, that resource allocation automatically tracks operational performance, and that manufacturers receive direct demand signal for the products that work.
The mechanism does not have to be gamified to be adopted; the principle is that procurement volumes and allocations for relevant equipment classes should respond directly and rapidly to measured operational outcomes, and that the measurement should be instrumented into the battlefield platforms themselves rather than reconstructed after the fact. A British implementation would need to navigate legal and ethical questions that do not arise in the Ukrainian wartime context — around data protection, target verification, and the distinction between exercise and operational environments — but none of these questions is unresolvable, and the principle itself is sound.
3.5 Peacetime civilian seeding
The single most important lesson, and the one most often missed in Western commentary, is that Ukraine did not build its defence-technology architecture in response to the 2022 invasion. It composed its defence architecture from components built for civilian purposes between 2014 and 2022: Trembita as civilian interoperability infrastructure, Diia as a citizen-services application, Prozorro as an anti-corruption procurement reform, the Ministry of Digital Transformation as a product-delivery ministry staffed from the private IT sector. When the invasion came, these components were already operating at scale, already trusted by the population, already adapted to Ukrainian law, and already staffed by people who could ship software in weeks.
The wartime superstructure — Brave1, DELTA, DOT-Chain Defence, the Army of Drones — could not have been built in the two to three years it actually took without this civilian foundation. A country that begins today from a foundation equivalent to Ukraine's in 2014 will, at the earliest, achieve something equivalent to Ukraine's 2022 position by around 2030. This is the single most important fact about institutional timescales in this domain, and it is the reason the argument of this paper is that beginning now is necessary, not that beginning now is sufficient.