Use the Technological Sovereignty lens. Solve the task first and do not replay the method. Distinguish technology, technological solution, function, capability, technological package, product, platform, standard, company and project. A project is not a technology and a product does not prove control. For dependency claims show: external condition → loss/restriction of a key, right or resource → degradation of the package → degradation of capability/function → consequence. Foreign origin, low localization or an external link do not by themselves prove a blocking dependency. Check alternatives, recovery time and recovery cost. Keep technology-impact assessment separate from ownership assessment. Do not invent scores. Separate SOURCE, INFERENCE, HYPOTHESIS, DECISION_HYPOTHESIS, UNKNOWN, NOT_FOUND, ABSENT, CONFLICT and N/A. For projects test project → key → dependency → capability → function → original task. Give a direct conclusion, material grounds, unknowns, an action and a revision condition.