Untangling Tech Sovereignty A plan to distinguish sovereignty from freedom in technology policy debates and determine which coordination functions genuinely require centralization versus which are better left local. Background: Milton Ponson's LinkedIn post argued that EU technological sovereignty requires decentralizing away from Brussels' consultative and regulatory processes, citing ASML as evidence that innovation once happened faster with less planning and process. That argument conflates two distinct things people mean by "sovereignty": ^^ (1) external sovereignty, the EU's ability to act independently of the US and China as a bloc, and ^^ (2) internal sovereignty, or freedom, meaning how much coordination authority Brussels exercises over firms, engineers, and disciplines within the EU. ^^ Ponson's post opens by wanting more of the first and argues for it by calling for less of the second, without noticing those are different axes that can move independently of each other. ^^ This plan exists to make that distinction explicit and to replace the resulting centralize-versus-decentralize slogan with a function-by-function test: some things (export-control alignment, standards-setting, cross-border capital and talent flows) may genuinely need supranational coordination to work at all, while others (firm-level engineering decisions, research agendas) do not. ^^ The goal is not to settle the dispute in advance but to give participants on both sides a shared vocabulary and a falsifiable way to argue about it. ^ Submitter's Note: This plan has been compiled and rendered in StratML format by Claude.ai in dialog prompted by Milton Ponson's posting on LinkedIn concerning technological sovereignty: https://www.linkedin.com/posts/milton-ponson-983979b_first-asml-baby-susanne-studied-veldhoven-activity-7478604954002255873-t2Kn?utm_source=share&utm_medium=member_desktop&rcm=ACoAAACRo-wBsB6AJXaqtz06r_wMwIYVUJtr0PM Sovereignty-Freedom Tradeoff Coalition SFTC be93604d-c8f9-4a02-a018-8722f8dd0284 A hypothetical group of individuals and organizations aiming to distinguish sovereignty from freedom in technology policy debates and determine which coordination functions genuinely require centralization versus which are better left local. Technology policy disputes are resolved by first clarifying which form of sovereignty or freedom is actually at stake, then testing centralization claims function by function rather than ideology by ideology. 2370b356-7957-480b-b8dd-bec8468a7c42 To provide a shared vocabulary and a function-level diagnostic that participants in tech-sovereignty debates can apply to their own disputes, replacing slogans with falsifiable claims about which coordination functions require which level of governance. 835bf42a-26cb-40d9-8fa9-8efdd21dbfc1 Clarity Distinguish terms that are commonly conflated, especially sovereignty (self-determination relative to outside powers) from freedom (autonomy relative to internal authority). Functional Subsidiarity Decide the right level of coordination by testing what a function actually requires, not by applying a blanket ideological preference for centralization or decentralization. Good Faith Present the strongest version of each side's argument before evaluating it, so engagement adds value rather than restating a prior position. Terminology Separate sovereignty and freedom into distinct, nameable axes so debate participants stop talking past each other. e2e9b0b4-d6b0-4671-ab19-1181f2e9da76 1 Terminological Clarity ~ Most disputes about tech sovereignty, including Ponson's post, use the single word "sovereignty" to cover at least two different claims: ^^ * independence from other blocs, and ^ * freedom from internal coordination. ^^ Because the word doesn't distinguish them, arguments can shift between the two meanings without anyone noticing, letting a call for less internal coordination masquerade as a case for more external independence when the two do not necessarily move together. ^^ This goal exists to give each meaning its own name before any function-level or engagement work happens, since the diagnostic in Goal 2 only works if "centralize" and "decentralize" are first tied to a specific, named claim rather than used as interchangeable synonyms for sovereignty in general. Sovereignties Separate external sovereignty (a bloc's independence from other powers) from internal sovereignty (who governs whom within the bloc), and name both explicitly whenever "sovereignty" is invoked. dd94223c-b9f1-458b-8241-6d43a163d48d 1.1 Distinguish Sovereignties: "Sovereignty" is routinely used to mean two different things. ^^ * External sovereignty is a bloc's independence relative to other blocs or powers — e.g., the EU not being dependent on US or Chinese chip fabrication or cloud infrastructure. ^ * Internal sovereignty is about who holds decision authority within the bloc — e.g., whether Brussels or individual member states, firms, and engineers make a given call. ^^ A speaker can consistently want more of one and less of the other; the failure mode is treating them as the same dial. Freedom Clarify that a call for more local autonomy is a claim about internal freedom, not automatically a claim that strengthens external sovereignty, and require arguments to specify which one they mean. 0cf545a6-4260-4d33-97c0-04ddf5ca2df1 1.2 Distinguish Freedom From Sovereignty: ^^ * Freedom here means local autonomy — a firm or engineer's latitude to act without seeking approval from a higher authority. It is a claim about internal governance, not about the bloc's standing relative to outside powers. ^^ Ponson's post treats more local freedom as if it straightforwardly produces more external sovereignty, but that is a separate empirical claim that needs its own argument: ^ * freeing local actors could strengthen the EU's competitive position, or it could fragment the coordination that external sovereignty actually depends on. ^^ Which one happens is an empirical question, not something settled by the word "sovereignty" alone. Functions Replace centralize-versus-decentralize sloganeering with a function-by-function test of what coordination level a given tech-policy activity actually requires. 22a1812b-64b5-4062-9104-c06a53c65dcc 2 Function-Level Diagnosis: ^ * Rather than asking whether the EU should be "more centralized" or "more decentralized" in general, this goal breaks tech policy into specific functions and asks, for each one, whether it actually requires coordination above the firm or member-state level to work. ^^ Some functions plausibly do (aligning export controls, setting interoperable technical standards, enabling cross-border capital and talent flows); others plausibly do not (day-to-day engineering and research decisions). ^^ Treating the question at the function level, rather than the ideology level, is what makes the diagnosis falsifiable instead of rhetorical. Coordination Identify which functions (e.g., export-control alignment, technical standards-setting, cross-border capital and talent flows, IP protection) plausibly require supranational coordination to work at all. a19bc695-4509-45ab-a17e-a455c692a359 2.1 Map Required Coordination: ^ * These are functions where uncoordinated local action plausibly cannot produce the outcome at all, because the function depends on many actors doing the same thing at once — e.g., an export-control regime only works if member states apply it consistently, a technical standard only creates interoperability if enough parties adopt it, and cross-border capital or talent mobility requires mutual recognition among jurisdictions. ^^ The test is not whether coordination is convenient but whether the function is achievable without it. Locality Identify which functions (e.g., firm-level engineering decisions, research agendas, day-to-day innovation choices) are best left to local actors without added central process. c4a2d27a-44cd-4ca0-93f3-463f0c35c4a7 2.2 Map Local Functions: ^ * These are functions where a central process adds review and delay without adding anything the function actually needs — e.g., which engineering approach a firm takes, which research questions a lab pursues, or how a team organizes its own work. ^^ Ponson's underlying complaint, that Brussels processes slow down decisions best made locally, most plausibly applies to functions in this category rather than to the ones in Map Required Coordination. Historical Claims Evaluate whether pre-regulatory success stories such as ASML are genuine evidence about the cost of current regulatory processes, or are confounded by other factors such as capital markets, talent mobility, and energy costs. bddb3d58-eccd-48b0-88ac-688a33623e9f 2.3 Test Historical Claims: ^ * Ponson cites ASML as evidence that European innovation used to happen through direct action rather than extensive planning, framing today's regulatory process as the cause of any relative slowdown. ^^ But ASML's formative years predate most of the current EU regulatory stack, and correlation between "less process in the past" and "more success in the past" does not establish that today's process is the active constraint, as opposed to other factors that also changed over the same period, such as capital markets depth, talent mobility, and energy costs. ^^ This objective is about checking that causal claim before accepting it, not about dismissing it. Dialogue Turn the framework into actual dialogue with participants in live disputes rather than a one-sided rebuttal. 9aa5f843-a754-4aec-82d9-7a8fc2465410 3 Constructive Engagement: ^ * The point of Goals 1 and 2 is to make the dispute more precise; this goal is about actually using that precision in dialogue with the people having the argument, rather than filing the framework away as a private analysis. ^^ That means presenting it to Ponson and others as a shared tool they can apply to their own position, not as a rebuttal aimed at declaring a winner. Balance Present the strongest deregulatory case (Hayekian knowledge problem, public-choice critique of self-perpetuating consultative processes) and the strongest protective case (regulation as citizen sovereignty against unaccountable concentrations of power) before drawing any conclusion. c374c6d7-5a53-4c57-b6e2-cd4848c844ad 3.1 Steelman Both Positions: "Steelmanning" means constructing the strongest, most charitable version of a position before responding to it — the opposite of a "strawman," where you argue against a weakened or distorted version of what someone actually said. Applied here: the strongest deregulatory case draws on the Hayekian knowledge problem (local actors hold tacit, situated knowledge that central planning cannot replicate) and the public-choice critique that consultative processes tend to become self-perpetuating and serve the coordinators more than the coordinated. The strongest protective case is that regulation such as the GDPR or the AI Act is itself an exercise of citizen sovereignty, protecting individuals and downstream firms from unaccountable concentrations of corporate or state power, which is a different freedom than the innovator's freedom to move fast. Doing both before concluding anything is what keeps this plan from being a disguised argument for one side. Commentary Engage original posters and commenters directly, offering the sovereignty/freedom distinction and function-level diagnostic as a tool they can apply, rather than arguing for a predetermined side. 79f5bacf-d4fc-479d-a149-4e2ac144f194 3.2 Invite Dialogue: Concretely, this means responding to Ponson's post and similar arguments by offering the sovereignty/freedom distinction and the function-level test as something the original poster and other commenters can use to sharpen their own argument, rather than posting a rebuttal that assumes the deregulatory position is simply wrong. The measure of success is whether the framework changes how the conversation proceeds, not whether it wins the thread. Related Work Link this framework explicitly to the Sovereignty Literacy (SLHV.xml) and Tradeoff Literacy (TRFL.xml) plans so readers can trace the underlying vocabulary. 9e75f8eb-8d33-4eea-afa0-6829c43fedb1 3.3 Cross-Reference Related Work: This plan applies vocabulary developed elsewhere rather than inventing new terms from scratch, so readers who want the fuller underlying argument for either distinction should consult these two plans directly. ^ * Sovereignty Literacy Heuristic Verification ~ https://stratml.us/docs/SLHV.xml ^ * Tradeoff Literacy ~ https://stratml.us/docs/TRFL.xml 2026-07-04 https://stratml.us/docs/UTS.xml Owen Ambur Owen.Ambur@verizon.net