Technology Is Statecraft: A Practical Agenda for Bharat

You may be deciding whether a new platform, computing partnership, public database or infrastructure contract is good for Bharat. Price, jobs and local assembly all matter. But they do not answer the decisive question: after the agreement is signed, who still has the power to say no?

That question now belongs in every technology decision. When payments, hospitals, ports, power grids and the machinery of government depend on computing, a technical dependency can become a political constraint. Use the framework below to distinguish ordinary commercial reliance from a loss of strategic freedom.

The real contest is control over capability

Technology policy was once treated mainly as economic policy. Governments promoted research, allocated spectrum, enforced competition rules and asked how much growth an industry might produce. That frame is now incomplete because computing is no longer confined to a recognisable technology sector. It is the operating layer beneath essential services.

A persuasive strategic reading of the October 7, 2022, US Commerce Department export regulation is that it sought to slow a rival’s technological progress by constraining the capability to produce, not merely by taxing or blocking finished goods. That distinction matters. A tariff changes the price of an exchange. Control over production capability can affect whether an exchange remains possible at all.

This is why country-of-origin labels are insufficient. A system can be assembled domestically while remaining dependent on external tools, licences, components, updates or specialised knowledge. Conversely, an imported product need not create a dangerous dependency if it can be replaced, maintained and operated through several genuinely independent routes.

Strategic autonomy therefore does not mean manufacturing everything within national borders. It means preserving usable choices under pressure. Apply a simple test: if a supplier, platform owner or foreign government withdrew access, could the essential service continue, migrate, be repaired or be replaced without surrendering a major policy choice? If the honest answer is no, you are no longer looking at a routine purchase. You are looking at statecraft.

Audit the dependency beneath every essential service

Begin with the public function, not the vendor. A catalogue of products tells you what an organisation bought; it does not tell you what the country could lose. The useful unit of analysis is an essential outcome such as processing a payment, operating a port, maintaining a medical service or administering a government function.

1. Name the function that must continue. Write it as an outcome that citizens or institutions depend on. Do not begin with a brand, product or ministry boundary.
2. Map the full operating chain. Include hardware, software, communications, identity, data, updates, maintenance, specialist skills and any permission required to keep the service running.
3. Mark every denial point. Ask who can revoke a licence, block an export, discontinue a component, force an incompatible update, change an interface, withhold documentation or prevent data from moving elsewhere.
4. Test the substitutes. An alternative is real only if it is technically compatible, contractually available, operationally deployable and supported by people who know how to use it. A vendor name on a slide is not a fallback.
5. State the consequence of failure. Distinguish an inconvenience from an interruption that could disable an essential service, expose sensitive data or narrow the government’s freedom to act.
6. Assign an accountable owner. One named office must be responsible for maintaining the dependency map, testing the exit path and reporting when a manageable reliance has become a strategic vulnerability.

The most common misreading is to equate domestic assembly with domestic control. Assembly can create employment and industrial experience, but it does not by itself confer the right or competence to modify, repair or reproduce the system. Ask what remains in Bharat after the contract ends: trained engineering teams, technical documentation, maintenance authority, production knowledge, interoperable data and the ability to qualify alternatives.

Run the same test on domestic suppliers. Nationality is not a substitute for resilience. A private monopoly, an opaque technical architecture or a contractor that cannot operate without an external platform can create a strategic dependency even when the invoice and corporate registration are Indian.

The audit must also be repeated. Vendors merge, licences change, skills leave, components become unavailable and software architectures evolve. A system that had a credible exit path when purchased may lose it later. Tie dependency review to renewal, major upgrades and changes in the operating chain rather than treating it as a one-time security exercise.

Choose what Bharat must build, buy and bargain for

Once the dependencies are visible, do not answer every risk with the slogan of self-sufficiency. Classify each capability by the consequence of denial and the practicality of substitution. That produces three different policy responses.

The build category should be narrow enough to be credible. Declaring every technology strategic spreads capital, talent and administrative attention too thinly. Give priority to capabilities whose denial would combine high public consequence with weak substitutability. A popular consumer product and an irreplaceable component of an essential service should not receive the same treatment merely because both are described as advanced technology.

The buy category still requires discipline. Procurement teams often compare price and performance while assuming continued access. Add portability, maintainability and supplier independence to the evaluation. A cheaper system can impose a larger strategic cost if leaving it later requires rebuilding data, retraining an entire workforce or interrupting an essential function.

The bargain category is where Bharat can turn market access into lasting capability. The test is not whether a partnership produces a ceremonial announcement or a domestic facility. Ask whether Indian teams gain responsibility for difficult work, whether local operators can maintain the system without permanent permission from outside, and whether the arrangement creates more choices at the end than existed at the beginning.

Public money should buy learning as well as output. When a subsidy, contract or partnership ends, the country should be able to identify the competence it retained. If the only durable result is installed equipment that cannot be independently maintained or adapted, the expenditure may have purchased capacity without purchasing autonomy.

A Dharmic state must protect citizens as well as systems

Dharma is not an adjective that makes every national technology project righteous. A state can reduce foreign dependence while concentrating arbitrary power at home. It can secure a database while denying a person any meaningful way to correct an error. It can build a national platform that is resilient against an external adversary yet opaque to the citizens expected to live under it.

A Dharmic judgment must examine both the purpose of power and the restraints placed upon it. Technology should preserve social order and legitimate public authority, but it should also protect dignity, plurality and avenues of redress. Strategic capability without accountability can strengthen the machinery of the state while weakening the polity it exists to serve.

For every essential digital system, conduct a two-column review. In the first column, record exposure to external coercion: denial of components, licences, updates, services, knowledge or data access. In the second, record exposure to internal misuse: unnecessary data collection, unreviewable automated decisions, unchecked privileged access, permanent emergency powers or the absence of a correction process. A proposal with either column left blank is not ready for strategic approval.

• Define the legitimate purpose. Specify the public function the system is permitted to serve. Capability accumulated without a bounded purpose invites reuse beyond the original justification.
• Collect only what the function requires. More data can increase administrative reach while also enlarging the consequences of misuse, error or compromise.
• Preserve a human path to correction. A person affected by an identity, eligibility or access decision should be able to understand the relevant decision and seek review.
• Log and review exceptional access. Privileged actions should leave an accountable record so that authority does not become invisible merely because it is exercised through software.
• Design for continuity beyond the centre. Local operators need documented procedures and workable fallbacks when a central platform or major contractor is unavailable.
• Measure capability left with the public. Training, maintenance competence and institutional knowledge matter because sovereignty cannot reside only in a contract or a small circle of vendors.

Protection from external pressure and protection from internal arbitrariness are not competing goals. Both require the same habit: identify where power is concentrated, limit unnecessary dependence, preserve alternatives and make the holder of power answerable for its use.

Key takeaways

• Technology becomes statecraft when an external decision can interrupt an essential function or narrow Bharat’s freedom to choose its policy.
• Local assembly is valuable but does not prove strategic control; maintenance rights, operating knowledge, substitutability and trained people matter more.
• Build selectively where denial would be severe and substitutes are weak. Diversify ordinary purchases, and bargain so partnerships leave durable competence behind.
• Review dependencies at renewal, major upgrades and changes in the operating chain. Resilience can decay even when the original design was sound.
• Judge sovereignty in two directions: resistance to foreign coercion and restraint against arbitrary power over citizens.

At the next procurement meeting, policy review or public debate, ask for a one-page dependency note before approving the technology. It should name the essential function, the points at which access can be denied, the tested fallback, the competence that will remain in Bharat and the safeguard available to an affected citizen. If those answers are missing, the proposal is not strategically mature.

Technology becomes statecraft long before a crisis makes the dependency visible. Bharat can strengthen its freedom one decision at a time by ensuring that each important contract leaves behind more capability, more choice and clearer accountability than it found.

References

• Hindu Post — The Statecraft of Technology